Messages in this thread | | | Subject | Re: Linux kernel file offset pointer races | From | Alan Cox <> | Date | Thu, 12 Aug 2004 22:12:24 +0100 |
| |
On Iau, 2004-08-12 at 22:38, Pavel Kankovsky wrote: > In this scenario, the 1st and 3rd pages read by read() contain the old > data (before write()) but the 2nd page contains the new data (after > write()). This is absurd.
Why ?
> BTW: What about writev() (esp. with O_APPEND)? It appears Linux > implementation makes it possible to interleave parts of writev() with > other writes.
If that can occur with O_APPEND it might be a bug. SuS does make some real guarantees about what O_APPEND means.
> Moreover, there appears to be a race condition between locks_verify_area() > and the actual I/O operation(s).
Details ?
- 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/
| |