diff options
author | Peter Staubach <staubach@redhat.com> | 2006-02-17 13:52:36 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-02-17 13:59:26 -0800 |
commit | b2f49033d80c952a0ffc2d5647bc1a0b8a09c1b3 (patch) | |
tree | 63a57e80389c1343e56150d31accf91829ce700a /drivers/char/tpm | |
parent | 614f8f50ca1361d054cdeca38d241684490d2296 (diff) | |
download | op-kernel-dev-b2f49033d80c952a0ffc2d5647bc1a0b8a09c1b3.zip op-kernel-dev-b2f49033d80c952a0ffc2d5647bc1a0b8a09c1b3.tar.gz |
[PATCH] fix deadlock in ext2
Fix a deadlock possible in the ext2 file system implementation. This
deadlock occurs when a file is removed from an ext2 file system which was
mounted with the "sync" mount option.
The problem is that ext2_xattr_delete_inode() was invoking the routine,
sync_dirty_buffer(), using a buffer head which was previously locked via
lock_buffer(). The first thing that sync_dirty_buffer() does is to lock
the buffer head that it was passed. It does this via lock_buffer(). Oops.
The solution is to unlock the buffer head in ext2_xattr_delete_inode()
before invoking sync_dirty_buffer(). This makes the code in
ext2_xattr_delete_inode() obey the same locking rules as all other callers
of sync_dirty_buffer() in the ext2 file system implementation.
Signed-off-by: Peter Staubach <staubach@redhat.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/char/tpm')
0 files changed, 0 insertions, 0 deletions