Skip to content
Snippets Groups Projects
  • Jan Kara's avatar
    0dc83bd3
    Revert "writeback: do not sync data dirtied after sync start" · 0dc83bd3
    Jan Kara authored
    
    This reverts commit c4a391b5. 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: default avatarJan Kara <jack@suse.cz>
    0dc83bd3
    History
    Revert "writeback: do not sync data dirtied after sync start"
    Jan Kara authored
    
    This reverts commit c4a391b5. 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: default avatarJan Kara <jack@suse.cz>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.