From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: adrian@smop.co.uk, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-mm1 leaks in dvb playback (found)
Date: 31 Mar 2006 03:22:35 +0200
Date: Fri, 31 Mar 2006 03:22:35 +0200 [thread overview]
Message-ID: <20060331012235.GB45568@muc.de> (raw)
In-Reply-To: <20060330.152821.24959319.davem@davemloft.net>
On Thu, Mar 30, 2006 at 03:28:21PM -0800, David S. Miller wrote:
> From: Adrian Bridgett <adrian@smop.co.uk>
> Date: Fri, 31 Mar 2006 00:11:31 +0100
>
> > On Thu, Mar 30, 2006 at 23:58:30 +0100 (+0100), adrian wrote:
> > > What I thought was just one patch was actually two and it was the
> > > other patch causing the problem - "Do not lose accepted socket when
> > > -ENFILE/-EMFILE".
> >
> > Hmm - it looks like it was meant to be reverted in 2.6.16-rc1-mm4,5 FWIW.
>
> So is the current version in Linus's tree causing this problem?
I don't know if it's this patch, but I definitely see a socket
leak here with linus tree at least since -git8. It unfortunately takes a day
or two to really trigger, so binary search would be difficult.
-Andi
next prev parent reply other threads:[~2006-03-31 1:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:15 2.6.16-mm1 leaks in dvb playback Adrian Bridgett
2006-03-28 1:23 ` Andrew Morton
2006-03-28 7:02 ` adrian
2006-03-28 7:16 ` Andrew Morton
2006-03-29 23:37 ` adrian
2006-03-30 0:06 ` Andrew Morton
2006-03-30 0:45 ` Adrian Bridgett
2006-03-30 22:58 ` 2.6.16-mm1 leaks in dvb playback (found) Adrian Bridgett
2006-03-30 23:11 ` Adrian Bridgett
2006-03-30 23:28 ` David S. Miller
2006-03-31 1:22 ` Andi Kleen [this message]
2006-03-31 7:28 ` Adrian Bridgett
2006-03-31 7:48 ` David S. Miller
2006-03-31 9:54 ` Adrian Bridgett
2006-03-31 10:07 ` David S. Miller
2006-03-31 18:47 ` Adrian Bridgett
2006-03-28 7:23 ` 2.6.16-mm1 leaks in dvb playback adrian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060331012235.GB45568@muc.de \
--to=ak@muc.de \
--cc=adrian@smop.co.uk \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.