How to implement a driver's read and write operations with synchronization properly
Anh Le
anhlq2110 at gmail.com
Tue Jul 29 09:59:08 EDT 2014
On Tue, Jul 29, 2014 at 7:47 PM, Jonathan Neuschäfer
<j.neuschaefer at gmx.net> wrote:
> I've tried this out myself, and it seems to be an issue with bash:
> As you can see, I observed the same pattern of 1008 and 993 bytes.
I think you're right. The split is done by the user program, separated
from kernel land. So I guess it's reasonable to use the 1st approach,
which is to always release the lock at the end of the operation. But
still, user programs like bash could have a race problem by spliting
the input, I hope that they can somehow take care of this problem
themselves.
Thanks guys.
--
Le Quoc Anh
More information about the Kernelnewbies
mailing list