diff options
| author | Glauber de Oliveira Costa <glommer@br.ibm.com> | 2005-10-30 15:02:48 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-10-30 17:37:23 -0800 |
| commit | 5b11687924e40790deb0d5f959247ade82196665 (patch) | |
| tree | 29aa104cc40bd2c85e7bba0f4b404b04cd6f207a /fs/ext3/inode.c | |
| parent | 2384f55f8aa520172c995965bd2f8a9740d53095 (diff) | |
| download | kernel_samsung_aries-5b11687924e40790deb0d5f959247ade82196665.zip kernel_samsung_aries-5b11687924e40790deb0d5f959247ade82196665.tar.gz kernel_samsung_aries-5b11687924e40790deb0d5f959247ade82196665.tar.bz2 | |
[PATCH] Locking problems while EXT3FS_DEBUG on
I noticed some problems while running ext3 with the debug flag set on.
More precisely, I was unable to umount the filesystem. Some investigation
took me to the patch that follows.
At a first glance , the lock/unlock I've taken out seems really not
necessary, as the main code (outside debug) does not lock the super. The
only additional danger operations that debug code introduces seems to be
related to bitmap, but bitmap operations tends to be all atomic anyway.
I also took the opportunity to fix 2 spelling errors.
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/ext3/inode.c')
| -rw-r--r-- | fs/ext3/inode.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/ext3/inode.c b/fs/ext3/inode.c index 8b38f22..b5da524 100644 --- a/fs/ext3/inode.c +++ b/fs/ext3/inode.c @@ -491,7 +491,7 @@ static unsigned long ext3_find_goal(struct inode *inode, long block, * the same format as ext3_get_branch() would do. We are calling it after * we had read the existing part of chain and partial points to the last * triple of that (one with zero ->key). Upon the exit we have the same - * picture as after the successful ext3_get_block(), excpet that in one + * picture as after the successful ext3_get_block(), except that in one * place chain is disconnected - *branch->p is still zero (we did not * set the last link), but branch->key contains the number that should * be placed into *branch->p to fill that gap. |