diff options
| author | Jeff Mahoney <jeffm@suse.com> | 2013-08-08 17:34:46 -0400 |
|---|---|---|
| committer | Jeff Mahoney <jeffm@suse.de> | 2013-08-08 17:34:46 -0400 |
| commit | 278f6679f454bf185a07d9a4ca355b153482d17a (patch) | |
| tree | ffead073e67cfdc1ddfc3949ebc93c06dcaaab8f /fs/reiserfs/prints.c | |
| parent | 4c05141df57f4ffc1a9a28f1925434924179bfe4 (diff) | |
| download | linux-278f6679f454bf185a07d9a4ca355b153482d17a.tar.bz2 | |
reiserfs: locking, handle nested locks properly
The reiserfs write lock replaced the BKL and uses similar semantics.
Frederic's locking code makes a distinction between when the lock is nested
and when it's being acquired/released, but I don't think that's the right
distinction to make.
The right distinction is between the lock being released at end-of-use and
the lock being released for a schedule. The unlock should return the depth
and the lock should restore it, rather than the other way around as it is now.
This patch implements that and adds a number of places where the lock
should be dropped.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Diffstat (limited to 'fs/reiserfs/prints.c')
| -rw-r--r-- | fs/reiserfs/prints.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/fs/reiserfs/prints.c b/fs/reiserfs/prints.c index c0b1112ab7e3..54944d5a4a6e 100644 --- a/fs/reiserfs/prints.c +++ b/fs/reiserfs/prints.c @@ -358,12 +358,13 @@ void __reiserfs_panic(struct super_block *sb, const char *id, dump_stack(); #endif if (sb) - panic(KERN_WARNING "REISERFS panic (device %s): %s%s%s: %s\n", + printk(KERN_WARNING "REISERFS panic (device %s): %s%s%s: %s\n", sb->s_id, id ? id : "", id ? " " : "", function, error_buf); else - panic(KERN_WARNING "REISERFS panic: %s%s%s: %s\n", + printk(KERN_WARNING "REISERFS panic: %s%s%s: %s\n", id ? id : "", id ? " " : "", function, error_buf); + BUG(); } void __reiserfs_error(struct super_block *sb, const char *id, |