[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1251167570-5233-5-git-send-email-fweisbec@gmail.com>
Date: Tue, 25 Aug 2009 04:32:50 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: LKML <linux-kernel@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Chris Mason <chris.mason@...cle.com>,
Roland Dreier <rdreier@...co.com>, Ingo Molnar <mingo@...e.hu>,
Andi Kleen <andi@...stfloor.org>,
Jeff Mahoney <jeffm@...e.com>,
Alexander Beregalov <a.beregalov@...il.com>,
Bron Gondwana <brong@...tmail.fm>,
Reiserfs <reiserfs-devel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Andrea Gelmini <andrea.gelmini@...il.com>,
"Trenton D. Adams" <trenton.d.adams@...il.com>,
Thomas Meyer <thomas@...3r.de>,
Alessio Igor Bogani <abogani@...ware.it>,
Marcel Hilzinger <mhilzinger@...uxnewmedia.de>,
Edward Shishkin <edward.shishkin@...il.com>,
Laurent Riffard <laurent.riffard@...e.fr>
Subject: [PATCH 4/4] kill-the-bkl/reiserfs: panic in case of lock imbalance
Until now, trying to unlock the reiserfs write lock whereas the current
task doesn't hold it lead to a simple warning.
We should actually warn and panic in this case to avoid the user datas
to reach an unstable state.
Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
Cc: Jeff Mahoney <jeffm@...e.com>
Cc: Chris Mason <chris.mason@...cle.com>
Cc: Ingo Molnar <mingo@...e.hu>
Cc: Alexander Beregalov <a.beregalov@...il.com>
Cc: Laurent Riffard <laurent.riffard@...e.fr>
---
fs/reiserfs/lock.c | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/fs/reiserfs/lock.c b/fs/reiserfs/lock.c
index cb1bba3..ee2cfc0 100644
--- a/fs/reiserfs/lock.c
+++ b/fs/reiserfs/lock.c
@@ -37,11 +37,10 @@ void reiserfs_write_unlock(struct super_block *s)
/*
* Are we unlocking without even holding the lock?
- * Such a situation could even raise a BUG() if we don't
- * want the data become corrupted
+ * Such a situation must raise a BUG() if we don't want
+ * to corrupt the data.
*/
- WARN_ONCE(sb_i->lock_owner != current,
- "Superblock write lock imbalance");
+ BUG_ON(sb_i->lock_owner != current);
if (--sb_i->lock_depth == -1) {
sb_i->lock_owner = NULL;
--
1.6.2.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists