summaryrefslogtreecommitdiffstats
path: root/arch/um/sys-x86_64/delay.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@redhat.com>2009-12-08 21:48:58 -0500
committerTheodore Ts'o <tytso@mit.edu>2009-12-08 21:48:58 -0500
commitd4edac314e9ad0b21ba20ba8bc61b61f186f79e1 (patch)
treeaf44b291976308b9db6c215cb2dc03bbe020d6fc /arch/um/sys-x86_64/delay.c
parentb9a4207d5e911b938f73079a83cc2ae10524ec7f (diff)
downloadkernel-crypto-d4edac314e9ad0b21ba20ba8bc61b61f186f79e1.tar.gz
kernel-crypto-d4edac314e9ad0b21ba20ba8bc61b61f186f79e1.tar.xz
kernel-crypto-d4edac314e9ad0b21ba20ba8bc61b61f186f79e1.zip
ext4: wait for log to commit when umounting
There is a potential race when a transaction is committing right when the file system is being umounting. This could reduce in a race because EXT4_SB(sb)->s_group_info could be freed in ext4_put_super before the commit code calls a callback so the mballoc code can release freed blocks in the transaction, resulting in a panic trying to access the freed s_group_info. The fix is to wait for the transaction to finish committing before we shutdown the multiblock allocator. Signed-off-by: Josef Bacik <josef@redhat.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'arch/um/sys-x86_64/delay.c')
0 files changed, 0 insertions, 0 deletions