From: David Miller <davem@davemloft.net>
To: kees.cook@canonical.com
Cc: netdev@vger.kernel.org
Subject: Re: shutdown(2) does not fully shut down socket any more
Date: Fri, 08 Apr 2011 15:31:30 -0700 (PDT) [thread overview]
Message-ID: <20110408.153130.226769035.davem@davemloft.net> (raw)
In-Reply-To: <20110408223004.GY4050@outflux.net>
From: Kees Cook <kees.cook@canonical.com>
Date: Fri, 8 Apr 2011 15:30:04 -0700
> Ah! Thanks, I didn't noticed that; I saw no activity on the bugzilla entry,
> so I thought it hadn't been seen yet.
We bascially do not use kernel.org bugzilla for bug tracking, all
work and discussions occur only here on the netdev list.
So what Stephen Hemminger, Andrew Morton, and others do is simply
forward the bug reports here to the list so we can work on them.
next prev parent reply other threads:[~2011-04-08 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 22:10 shutdown(2) does not fully shut down socket any more Kees Cook
2011-04-08 22:24 ` David Miller
2011-04-08 22:30 ` Kees Cook
2011-04-08 22:31 ` David Miller [this message]
2011-04-08 22:46 ` Kees Cook
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=20110408.153130.226769035.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kees.cook@canonical.com \
--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