On Sun, Feb 05, 2012 at 03:14:21PM -0600, Tyler Hicks wrote: > From: Li Wang <[email protected]> > > [ Upstream commit 684a3ff7e69acc7c678d1a1394fe9e757993fd34 ] > > ecryptfs_write() can enter an infinite loop when truncating a file to a > size larger than 4G. This only happens on architectures where size_t is > represented by 32 bits. > > This was caused by a size_t overflow due to it incorrectly being used to > store the result of a calculation which uses potentially large values of > type loff_t. > > [[email protected]: rewrite subject and commit message] > Signed-off-by: Li Wang <[email protected]> > Signed-off-by: Yunchuan Wen <[email protected]> > Reviewed-by: Cong Wang <[email protected]> > Signed-off-by: Tyler Hicks <[email protected]> > --- > > Hello - This is the "backport" to 3.2.4, which also applies to 3.0.19 with no > problem. It required no backporting (just a cherry-pick), so I'm not sure why > I > received a "FAILED" message from Greg. Let me know if I'm doing something > wrong. :)
It failed because the original patch did not apply cleanly, but you fixed that up in this resend, thanks. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
