aboutsummaryrefslogtreecommitdiffstats
path: root/fs/bfs
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@sandeen.net>2010-08-01 17:33:29 -0400
committerTheodore Ts'o <tytso@mit.edu>2010-08-01 17:33:29 -0400
commit437f88cc031ffe7f37f3e705367f4fe1f4be8b0f (patch)
tree0b3ab55db25c0ac8695b27858013388ff4bcc8a9 /fs/bfs
parent4538821993f4486c76090dfb377c60c0a0e71ba3 (diff)
downloadkernel_samsung_smdk4412-437f88cc031ffe7f37f3e705367f4fe1f4be8b0f.zip
kernel_samsung_smdk4412-437f88cc031ffe7f37f3e705367f4fe1f4be8b0f.tar.gz
kernel_samsung_smdk4412-437f88cc031ffe7f37f3e705367f4fe1f4be8b0f.tar.bz2
ext4: fix freeze deadlock under IO
Commit 6b0310fbf087ad6 caused a regression resulting in deadlocks when freezing a filesystem which had active IO; the vfs_check_frozen level (SB_FREEZE_WRITE) did not let the freeze-related IO syncing through. Duh. Changing the test to FREEZE_TRANS should let the normal freeze syncing get through the fs, but still block any transactions from starting once the fs is completely frozen. I tested this by running fsstress in the background while periodically snapshotting the fs and running fsck on the result. I ran into occasional deadlocks, but different ones. I think this is a fine fix for the problem at hand, and the other deadlocky things will need more investigation. Reported-by: Phillip Susi <psusi@cfl.rr.com> Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/bfs')
0 files changed, 0 insertions, 0 deletions