Kirk McKusick 5ecba76999 Historically when an application wrote an entire block of a file, ... the kernel allocated a buffer but did not zero it as it was about to be completely filled by a uiomove() from the user's buffer. However, if the uiomove() failed, the old contents of the buffer could be exposed especially if the file was being mmap'ed. The fix was to always zero the buffer when it was allocated. This change first attempts the uiomove() to the newly allocated (and dirty) buffer and only zeros it if the uiomove() fails. The effect is to eliminate the gratuitous zeroing of the buffer in the usual case where the uiomove() successfully fills it. Reviewed by: kib Tested by: scottl MFC after: 2 weeks (to 9 only)		2012-02-09 22:34:16 +00:00
..
ffs	Historically when an application wrote an entire block of a file,	2012-02-09 22:34:16 +00:00
ufs	Sprinkle missed calls to asynchronous UFS_UPDATE() in attempt to	2012-02-07 09:51:41 +00:00