From: Matthias Andree <matthias.andree@gmx.de>
To: David Miller <davem@davemloft.net>
Cc: ilpo.jarvinen@helsinki.fi, elendil@planet.nl, netdev@vger.kernel.org
Subject: Re: [PATCH v2] tcp: fix MSG_PEEK race check
Date: Tue, 19 May 2009 11:05:17 +0200 [thread overview]
Message-ID: <4A12764D.4010600@gmx.de> (raw)
In-Reply-To: <20090518.150433.92463181.davem@davemloft.net>
David Miller schrieb:
> Since I now understand your urg_hole code I'm going to apply your v2
> patch which takes care of the URG stuff. I also buy the argument that
> perhaps we should get rid of the log message, but look at how it
> helped us find this kernel regression :-)
Hi,
...and this discovery is a reason to leave it in, and perhaps make sure
that the check code is properly linked (through comments for lack of better
means) to the actual data transfer functions.
Cheers
MA
prev parent reply other threads:[~2009-05-19 9:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200902262310.12791.elendil@planet.nl>
[not found] ` <200903091749.50818.elendil@planet.nl>
[not found] ` <op.uqjiqsol1e62zd@merlin.emma.line.org>
[not found] ` <200903141900.14498.elendil@planet.nl>
2009-05-06 16:15 ` Strange Application bug, race in MSG_PEEK complaints (was: Bug#513695: fetchmail: race in MSG_PEEK) Matthias Andree
2009-05-06 23:02 ` Matthias Andree
2009-05-07 6:48 ` Ilpo Järvinen
2009-05-07 17:16 ` Frans Pop
2009-05-07 18:48 ` Ilpo Järvinen
2009-05-07 20:43 ` Frans Pop
2009-05-09 18:14 ` Frans Pop
2009-05-11 6:32 ` [PATCH v2] tcp: fix MSG_PEEK race check Ilpo Järvinen
2009-05-11 12:50 ` Frans Pop
2009-05-11 13:32 ` Ilpo Järvinen
2009-05-11 13:54 ` Frans Pop
2009-05-11 14:57 ` Ilpo Järvinen
2009-05-17 22:31 ` David Miller
2009-05-18 8:02 ` Matthias Andree
2009-05-17 22:41 ` David Miller
2009-05-18 7:24 ` Ilpo Järvinen
2009-05-18 15:34 ` Matthias Andree
2009-05-18 22:04 ` David Miller
2009-05-19 4:33 ` Ilpo Järvinen
2009-05-19 4:40 ` David Miller
2009-05-19 9:05 ` Matthias Andree [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=4A12764D.4010600@gmx.de \
--to=matthias.andree@gmx.de \
--cc=davem@davemloft.net \
--cc=elendil@planet.nl \
--cc=ilpo.jarvinen@helsinki.fi \
--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).