And if the bug is indeed that a FSYNC followed by no activity causes the
Kindle to disconnect, then the fix is simple, the kernel should ensure
it sends some harmless keep-alive type command after the FSYNC. Hell, if
that is indeed the case, then I can probably have calibre touch a file
on the device after every fsync to work around this issue. nobarrier is
not going to happen however.
And if the bug is indeed that a FSYNC followed by no activity causes the
Kindle to disconnect, then the fix is simple, the kernel should ensure
it sends some harmless keep-alive type command after the FSYNC. Hell, if
that is indeed the case, then I can probably have calibre touch a file
on the device after every fsync to work around this issue. nobarrier is
not going to happen however.