On Wednesday 18 June 2008 07:46, Linus Torvalds wrote:
Yes, the new filemap.c code does not require an exact byte count, but
it won't work if there is an under-estimation of the number of bytes
left to copy.
The old filemap.c code actually also relies on the byte count in some
cases, I can't remember off the top of my head, but I *think* it was a
security measure to prevent uninitialized data leak.
Most other cases of course only care about complete success or not, but
there are others. filemap_xip, splice are a couple that pop up.
Thanks for working that all out before I even read my email :)
--