From 0b788f40acb653d06db4c65b3c00a622383b3a48 Mon Sep 17 00:00:00 2001
From: Frederic Weisbecker <fweisbec@gmail.com>
Date: Tue, 25 Aug 2009 04:18:06 +0200
Subject: [PATCH] --- yaml --- r: 173179 b: refs/heads/master c:
 80503185989b2dd84170bb842e23d3fd45ebdf40 h: refs/heads/master i:   173177:
 01039ac604745c6d7bf897a1373ba50b8414e5e4   173175:
 9bafd82befae2459d5c67daaf64b9f8552731ea5 v: v3

---
 [refs]                   | 2 +-
 trunk/fs/reiserfs/lock.c | 7 +++----
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/[refs] b/[refs]
index 31a7a79618b9..301b9fc4ea87 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 7e94277050e31aa4204060f03953bba72598cf7d
+refs/heads/master: 80503185989b2dd84170bb842e23d3fd45ebdf40
diff --git a/trunk/fs/reiserfs/lock.c b/trunk/fs/reiserfs/lock.c
index cb1bba3802dd..ee2cfc0fd8a7 100644
--- a/trunk/fs/reiserfs/lock.c
+++ b/trunk/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;