aboutsummaryrefslogtreecommitdiffstats
path: root/fs/jbd/recovery.c
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2013-03-27 17:30:59 +0100
committerJan Kara <jack@suse.cz>2013-03-27 17:30:59 +0100
commite678a4f0f50d4fa4f7aaa6de8eb3f071513356a0 (patch)
tree94eafb0a1181006633817a65038d4923cc3e647a /fs/jbd/recovery.c
parentext3: fix data=journal fast mount/umount hang (diff)
downloadlinux-dev-e678a4f0f50d4fa4f7aaa6de8eb3f071513356a0.tar.xz
linux-dev-e678a4f0f50d4fa4f7aaa6de8eb3f071513356a0.zip
jbd: don't wait (forever) for stale tid caused by wraparound
In the case where an inode has a very stale transaction id (tid) in i_datasync_tid or i_sync_tid, it's possible that after a very large (2**31) number of transactions, that the tid number space might wrap, causing tid_geq()'s calculations to fail. Commit d9b0193 "jbd: fix fsync() tid wraparound bug" attempted to fix this problem, but it only avoided kjournald spinning forever by fixing the logic in jbd_log_start_commit(). Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/jbd/recovery.c')
0 files changed, 0 insertions, 0 deletions