Jan Kara 0dc83bd30b Revert "writeback: do not sync data dirtied after sync start" ... This reverts commit c4a391b53a. Dave Chinner <david@fromorbit.com> has reported the commit may cause some inodes to be left out from sync(2). This is because we can call redirty_tail() for some inode (which sets i_dirtied_when to current time) after sync(2) has started or similarly requeue_inode() can set i_dirtied_when to current time if writeback had to skip some pages. The real problem is in the functions clobbering i_dirtied_when but fixing that isn't trivial so revert is a safer choice for now. CC: stable@vger.kernel.org # >= 3.13 Signed-off-by: Jan Kara <jack@suse.cz>		2014-02-22 02:02:28 +01:00
..
events	Revert "writeback: do not sync data dirtied after sync start"	2014-02-22 02:02:28 +01:00
define_trace.h
ftrace.h	tracing: Consolidate event trigger code	2014-01-09 21:20:07 -05:00
syscall.h