From: adrian <adrian@smop.co.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-mm1 leaks in dvb playback
Date: Thu, 30 Mar 2006 00:37:12 +0100 [thread overview]
Message-ID: <20060329233712.GA21810@smop.co.uk> (raw)
In-Reply-To: <20060327231630.76e97b83.akpm@osdl.org>
On Mon, Mar 27, 2006 at 23:16:30 -0800 (-0800), Andrew Morton wrote:
> It's unlikely that the sock_inode_cache leak is related to the dcache leak,
> but we won't know until we know...
Looks like this might be the same issus as "dcache leak in 2.6.16-git8
(II)"...
I think I've found the patch which causes the leak - it was the
"use fget_light() in net/socket.c" patch. I can't see anything
obviously wrong, although the patch changes the code so that in
sys_sendto and sys_recvfrom it now does a sockfd_put(sock) if the
sock_from_file call fails which didn't use to happen. That seems to
agree more with other bits of code, but I've no idea what is the right
thing todo.
One item I spotted whilst perusing the code is that in net/core/sock.c
in compat_sock_common_getsockopt, it checks if
sk->sk_prot->compat_setsockopt is NULL before calling
sk->sk_prot->compat_getsockopt (set vs get).
I'll try and confirm tomorrow with a nice fresh build. The command
I'm using to test is "dvbstream -f 650166.670 -v 570 -a 571 -o >
/dev/null"
Thanks,
Adrian
next prev parent reply other threads:[~2006-03-29 23:37 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 [this message]
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
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=20060329233712.GA21810@smop.co.uk \
--to=adrian@smop.co.uk \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox