lkml.org 
[lkml]   [2004]   [Feb]   [6]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateFri, 6 Feb 2004 16:54:58 -0300
FromWerner Almesberger <>
SubjectRe: VFS locking: f_pos thread-safe ?
Matthias Urlichs wrote:
> but it's NOT AT ALL obvious to a "normal" application programmer.

It gets worse. From the same draft (perhaps someone who has the final
version could comment ?), in the rationale for read():

| The standard developers considered adding atomicity requirements to a
| pipe or FIFO, but recognized that due to the nature of pipes and FIFOs
| there could be no guarantee of atomicity of reads of {PIPE_BUF} or any
| other size that would be an aid to applications portability.

But then

| I/O is intended to be atomic to ordinary files and pipes and FIFOs.

Now, what exactly does "intended" mean ?

Of course, in this part, they only talk about data staying together,
not whether it can get duplicated, or effects on f_pos.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
\
 
 \ /
  Last update: 2005-03-22 14:00    [W:1.341 / U:0.030 seconds]
©2003-2008 Jasper Spaans