I think that's just printk's non-atomicity.
As best I recall, the value write() returns always represents a
contiguous stream of bytes written to the file descriptor (so that
chunk will be atomic, but it may be less than the whole buffer you
asked to be written), and for things like pipes/sockets and local
files opened with O_APPEND, write()'s are guaranteed to be
non-overlapping.
Corrections, anyone?
Adam
-- You crucify all honesty \\Adam D. Bradley artdodge@cs.bu.edu No signs you see do you believe \\Boston University Computer Science And all your words just twist and turn\\ Grad Student and Linux Hacker Reviving just to crash and burn \\ <>< ---------> Why can't you listen as love screams everywhere? <--------
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu