| To: | erik@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Demonstration code on how to trigger tcp6_sock leak |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
| Date: | Sun, 25 Jan 2004 14:25:26 +0900 (JST) |
| Cc: | netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx, usagi-core@xxxxxxxxxxxxxx |
| In-reply-to: | <20040124131307.GB2666@xxxxxxxxxxxxxxxxxxxxxxx> |
| Organization: | USAGI Project |
| References: | <20040124131307.GB2666@xxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <20040124131307.GB2666@xxxxxxxxxxxxxxxxxxxxxxx> (at Sat, 24 Jan 2004 14:13:07 +0100), Erik Hensema <erik@xxxxxxxxxxx> says: > I wrote some quick&dirty code showing the tcp6_sock leak in Linux 2.6.x. > The server part listens for incoming connections and accept()'s them. The > client will simply connect() to the server and close the connection. Okay, I confirm that there're something wrong with tcp6 socket. I'll look into it as soon as possible. --yoshfuji |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [update] 2.6.2-rc1 - Realtek 8169 patches, Srihari Vijayaraghavan |
|---|---|
| Next by Date: | [janitor] tc35815: handle ioremap() failure, Randy.Dunlap |
| Previous by Thread: | Demonstration code on how to trigger tcp6_sock leak, Erik Hensema |
| Next by Thread: | FIX (was Re: Demonstration code on how to trigger tcp6_sock leak), David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |