From: "David S. Miller" <davem@redhat.com>
To: shemminger@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Possible FIFO race in lock_sock()
Date: Fri, 28 Feb 2003 17:01:24 -0800 (PST) [thread overview]
Message-ID: <20030228.170124.03146870.davem@redhat.com> (raw)
In-Reply-To: <1046467548.30194.258.camel@dell_ss3.pdx.osdl.net>
From: Stephen Hemminger <shemminger@osdl.org>
Date: 28 Feb 2003 13:25:50 -0800
Don't know what this impacts, perhaps out of order data on a pipe?
There's a race to get the lock, who cares?
If multiple people are playing with the socket, the exact pieces of
data they happen to get is random unless the application does
it's own locking.
next prev parent reply other threads:[~2003-03-01 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 21:25 Possible FIFO race in lock_sock() Stephen Hemminger
2003-03-01 1:01 ` David S. Miller [this message]
2003-03-03 20:38 ` Steve Hocking
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=20030228.170124.03146870.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).