From: Brian Haley <brian.haley@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: don't call upper-layer disconnect function if not connected
Date: Wed, 02 Aug 2006 12:04:22 -0400 [thread overview]
Message-ID: <44D0CD06.3020201@hp.com> (raw)
In-Reply-To: <20060801.150753.78709843.davem@davemloft.net>
> The socket could have been bind()'d to, in which case it will
> not move to connected state and we still need to invoke
> the disconnect methods such as udp_disconnect() to clear out
> that binding.
Ok.
> You seem to be groveling in random areas of the ipv4 and ipv6 stack,
> what are you working on?
Was looking into a customer-reported memory leak that seemed to be in
this code path. It wasn't, but this tweak seemed sane at the time.
-Brian
prev parent reply other threads:[~2006-08-02 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 19:48 [PATCH] ipv4: don't call upper-layer disconnect function if not connected Brian Haley
2006-08-01 22:07 ` David Miller
2006-08-02 16:04 ` Brian Haley [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=44D0CD06.3020201@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).