From: Pavel Machek <pavel@suse.cz>
To: Kai Henningsen <kaih@khms.westfalen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VFS locking: f_pos thread-safe ?
Date: Thu, 19 Feb 2004 16:14:41 +0100 [thread overview]
Message-ID: <20040219151441.GD467@openzaurus.ucw.cz> (raw)
In-Reply-To: <92VRVYaHw-B@khms.westfalen.de>
Hi!
> POSIX says on <http://www.opengroup.org/onlinepubs/007904975/functions/
> read.html>:
>
> [...]
> DESCRIPTION
>
> The read() function shall attempt to read nbyte bytes from the file
> associated with the open file descriptor, fildes, into the buffer pointed
> to by buf. The behavior of multiple concurrent reads on the same pipe,
> FIFO, or terminal device is unspecified.
...which implies that concurrent reads on regular files are okay :-P.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-02-23 13:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 9:09 VFS locking: f_pos thread-safe ? Matt
2004-02-06 9:16 ` Andrew Morton
2004-02-06 9:26 ` Matt
2004-02-06 9:35 ` Andrew Morton
2004-02-06 10:19 ` Matthias Urlichs
2004-02-06 11:18 ` viro
2004-02-06 18:59 ` Matthias Urlichs
2004-02-06 19:54 ` Werner Almesberger
2004-02-08 15:58 ` Kai Henningsen
2004-02-19 15:14 ` Pavel Machek [this message]
[not found] ` <20040206101941.4cd9c882.shemminger@osdl.org>
2004-02-06 18:47 ` Matthias Urlichs
2004-02-06 13:50 ` Werner Almesberger
2004-02-06 13:56 ` viro
2004-02-06 14:24 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 7:12 Werner Almesberger
2004-02-06 7:55 ` Andrew Morton
2004-02-06 18:37 ` Joel Becker
2004-02-06 19:05 ` Matthias Urlichs
2004-02-07 1:35 ` Joel Becker
2004-02-06 20:09 ` Werner Almesberger
2004-02-06 20:56 ` Valdis.Kletnieks
2004-02-07 0:55 ` Werner Almesberger
2004-02-06 20:54 ` Andries Brouwer
2004-02-07 23:45 ` Werner Almesberger
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=20040219151441.GD467@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=kaih@khms.westfalen.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.