From: "Dan A. Dickey" <dan.dickey@savvis.net>
To: "David S. Miller" <davem@redhat.com>
Cc: <m.c.p@kernel.linux-systeme.com>, <linux-kernel@vger.kernel.org>,
<kuznet@ms2.inr.ac.ru>
Subject: Re: Sock leak in net/ipv4/af_inet.c - 2.4.26
Date: Tue, 11 May 2004 14:55:11 -0500 [thread overview]
Message-ID: <200405111455.11935.dan.dickey@savvis.net> (raw)
In-Reply-To: <20040511115934.0c591667.davem@redhat.com>
On Tuesday 11 May 2004 13:59, David S. Miller wrote:
> The sk_free() should occur when the final sock_put() call brings the count
> down to zero, then the socket destroy function is called and the eventual
> sk_free() occurs there.
Yes, I'm figuring this out.
I think my earlier report of this problem was a bit premature.
I'm refining my debug code and will let you know what I find.
-Dan
--
Dan A. Dickey
dan.dickey@savvis.net
prev parent reply other threads:[~2004-05-11 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 16:24 Sock leak in net/ipv4/af_inet.c - 2.4.26 Dickey, Dan
2004-05-11 16:43 ` Marc-Christian Petersen
2004-05-11 17:25 ` Dan A. Dickey
2004-05-11 18:59 ` David S. Miller
2004-05-11 19:55 ` Dan A. Dickey [this message]
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=200405111455.11935.dan.dickey@savvis.net \
--to=dan.dickey@savvis.net \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@kernel.linux-systeme.com \
/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