Re: do_loop_readv_writev() not as described for drivers implementing only write()?

From: Ulrich Drepper
Date: Wed Mar 03 2010 - 20:53:13 EST

On Wed, Mar 3, 2010 at 04:11, Daniel Baluta <daniel.baluta@xxxxxxxxx> wrote:
> I would say that the libc enforces atomicity,

Not at all. Any such implementation would unconditionally have to use
file locking and that's only a convention, not a requirement. The
libc only tries to work around a missing writev syscall.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at