linux-kernel - [PATCH 1/1] s

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1233241209-12782-1-git-send-email-hooanon05@yahoo.co.jp>
Date:	Fri, 30 Jan 2009 00:00:09 +0900
From:	"J. R. Okajima" <hooanon05@...oo.co.jp>
To:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Cc:	"J. R. Okajima" <hooanon05@...oo.co.jp>
Subject: [PATCH 1/1] s_umount in sget()

It seems to be forgotten to release s_umount rwsem in a error path of
sget(). I don't think it harmful generally since the rwsem is freed. But
I am afarid unnecessary info left in some debugging subsystem (lockdep
or something).

Signed-off-by: J. R. Okajima <hooanon05@...oo.co.jp>
---
 fs/super.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/fs/super.c b/fs/super.c
index 645e540..0331ff9 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -372,6 +372,7 @@ retry:
 	err = set(s, data);
 	if (err) {
 		spin_unlock(&sb_lock);
+		up_write(&s->s_umount);
 		destroy_super(s);
 		return ERR_PTR(err);
 	}
-- 
1.6.1.284.g5dc13

--
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/