On Wed 2014-07-23 16:26:41, Theodore Ts'o wrote:
> I don't think this patch is worthwhile. There is no legitimate reason
> to be using such large reads like this, and read(2) is always allowed
> to return a short read (for example, if a signal comes in while the
> read is happening). The only difference is that we are now guaranteed
> to return a short-read if you try to read more than 32MB. Given
Regression from previous versions would be the reason. I'm pretty sure
someone has that dd in the scripts somewhere. (And signals are not an
issue in dd case.)
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
