[Bugme-janitors] [Bug 10596] read, readv, write and writev system calls are not atomic

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=10596





------- Comment #9 from mtk.manpages at gmail.com  2008-05-21 08:54 -------
(In reply to comment #8)
> Why do you have trouble triggering non-atomic? I think thread-unsafety is
> enough to prove non-atomicity.

Perhaps I'm getting too hung up on a particular case.  If we do a vectored
write (writev()), I'm expecting that the non-atomicity might mean that output
bu other threads may be interspersed with the output of our writev().  Is that
a possibility?  If yes, I'm puzzled that I can' reproduce it.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.