public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: Nemo Publius <nemo@self-evident.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Does Linux select() violate POSIX?
Date: Sun, 19 Jun 2011 16:41:48 +0200	[thread overview]
Message-ID: <1308494508.13047.4.camel@thorin> (raw)
In-Reply-To: <BANLkTi=bvmtkv-o3PROYjmOwkBNCBFGv7w@mail.gmail.com>

On Sam, 2011-06-18 at 11:51 -0700, Nemo Publius wrote:
[...] 
> With any "test something, then assume result of test" sequence,
> obviously I can have race conditions with multiple processes or
> threads.  I mean, had I asked, "I call write() and then lseek() to

ACK.

> where I started and then read() on a file; am I guaranteed to read
> back what I wrote?"  And you said no, because some other process could
> write in the meantime...  I would say that is technically true but not
> at all what I was asking.

Then you should reformulate your question because the answer is
technically correct.
If the (technically correct!) answer does not help you, you asked the
wrong question.
It's as simple as that.

Kind regards,
Bernd
-- 
Bernd Petrovitsch                  Email : bernd@petrovitsch.priv.at
                     LUGA : http://www.luga.at


  reply	other threads:[~2011-06-19 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 17:06 Does Linux select() violate POSIX? Nemo Publius
2011-06-18 17:43 ` Eric Dumazet
2011-06-18 18:22   ` Nemo Publius
2011-06-18 18:33     ` Alan Cox
2011-06-18 18:51       ` Nemo Publius
2011-06-19 14:41         ` Bernd Petrovitsch [this message]
2011-06-19 22:21           ` Nemo Publius
2011-06-19 22:32             ` Alan Cox
2011-06-19 22:45               ` Nemo Publius
2011-06-22 18:20 ` Chris Friesen

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=1308494508.13047.4.camel@thorin \
    --to=bernd@petrovitsch.priv.at \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nemo@self-evident.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