diff options
| author | Ram Pai <linuxram@us.ibm.com> | 2005-11-07 17:17:04 -0500 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-11-07 18:18:10 -0800 |
| commit | 70fbcdf4d252c6b17cc249cb9ac9b220cb0b863d (patch) | |
| tree | cefa087774953dd7a2181513427577286f8e9f63 /kernel/crash_dump.c | |
| parent | 5b83d2c5c0afcf5a3517cf00d9ceb41b8345e01b (diff) | |
| download | op-kernel-dev-70fbcdf4d252c6b17cc249cb9ac9b220cb0b863d.zip op-kernel-dev-70fbcdf4d252c6b17cc249cb9ac9b220cb0b863d.tar.gz | |
[PATCH] umount_tree() locking change
umount is done under the protection of the namespace semaphore. This
can lead to intresting deadlocks when the last reference to a mount is
released, if filesystem code is in sufficiently nasty state.
This collects all the to-be-released-mounts and releases them after
releasing the namespace semaphore. That both reduces the time we are
holding namespace semaphore and gets the things more robust.
Idea proposed by Al Viro.
Signed-off-by: Ram Pai <linuxram@us.ibm.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'kernel/crash_dump.c')
0 files changed, 0 insertions, 0 deletions
