From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: davem@davemloft.net
Cc: shemminger@osdl.org, mitch@sfgoth.com, kernel@linuxace.com,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] fix select() for SOCK_RAW sockets (ipv6)
Date: Wed, 08 Dec 2004 16:58:50 +0900 (JST) [thread overview]
Message-ID: <20041208.165850.97660819.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20041207104815.3f7a4684.davem@davemloft.net>
In article <20041207104815.3f7a4684.davem@davemloft.net> (at Tue, 7 Dec 2004 10:48:15 -0800), "David S. Miller" <davem@davemloft.net> says:
> On Tue, 7 Dec 2004 10:01:40 -0800
> Stephen Hemminger <shemminger@osdl.org> wrote:
>
> > > Probably, we need to do the same for ipv6, don't we?
> >
> > diff -Nru a/net/ipv6/af_inet6.c b/net/ipv6/af_inet6.c
> > --- a/net/ipv6/af_inet6.c 2004-12-07 10:02:50 -08:00
> > +++ b/net/ipv6/af_inet6.c 2004-12-07 10:02:50 -08:00
> > @@ -513,6 +513,27 @@
>
> We didn't do the "UDP select() fix" on ipv6 because we don't
> have the delayed checksumming optimization there. So the
> ipv6 side really doesn't need this change.
Ok, thanks for the explanation.
--yoshfuji @ Strasbourg
next prev parent reply other threads:[~2004-12-08 7:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 0:35 Recent select() handling change breaks Poptop Phil Oester
2004-12-07 2:52 ` Mitchell Blank Jr
2004-12-07 4:53 ` Phil Oester
2004-12-07 5:48 ` Mitchell Blank Jr
2004-12-07 15:08 ` [PATCH] fix select() for SOCK_RAW sockets Mitchell Blank Jr
2004-12-07 17:28 ` Phil Oester
2004-12-07 17:35 ` YOSHIFUJI Hideaki / 吉藤英明
2004-12-07 18:01 ` [PATCH] fix select() for SOCK_RAW sockets (ipv6) Stephen Hemminger
2004-12-07 18:48 ` David S. Miller
2004-12-07 18:56 ` Stephen Hemminger
2004-12-08 7:58 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2004-12-07 17:45 ` [PATCH] fix select() for SOCK_RAW sockets Stephen Hemminger
2004-12-08 5:28 ` David S. Miller
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=20041208.165850.97660819.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=kernel@linuxace.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mitch@sfgoth.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®