linux-kernel - Re: [PATCH 02/16] GFS2: Core locking interface

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Pine.LNX.4.61.0609041108570.11217@yvahk01.tjqt.qr>
Date:	Mon, 4 Sep 2006 11:22:02 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Steven Whitehouse <swhiteho@...hat.com>
cc:	linux-kernel@...r.kernel.org,
	Russell Cattelan <cattelan@...hat.com>,
	David Teigland <teigland@...hat.com>,
	Ingo Molnar <mingo@...e.hu>, hch@...radead.org
Subject: Re: [PATCH 02/16] GFS2: Core locking interface

Hi,


>Unfortunately thats not possible as the struct gfs2_sbd is actually
>changed lower down the call chain, but only in the lock_dlm module.

+void gfs2_lm_unmount(struct gfs2_sbd *sdp)
+{
+	if (likely(!test_bit(SDF_SHUTDOWN, &sdp->sd_flags)))
+		gfs2_unmount_lockproto(&sdp->sd_lockstruct);
+}

I can't follow... test_bit does not modify *sdp or sdp->sd_flags, and
gfs2_unmount_lockproto does not either.


>http://www.kernel.org/git/?p=linux/kernel/git/steve
/gfs2-2.6.git;a=commitdiff;h=5029996547a9f3988459e11955c13259495308ef

(Argh for browsers: while copy-and-paste from firefox to xterm compresses all
spaces (like s/ +/ /g), MSIE displays it compressed right away. The latter is
caused because it does not support the white-space:pre; CSS attribute. A
workaround for both browsers is to s/  / &nbsp;/g)



Jan Engelhardt
-- 

-- 
VGER BF report: H 0.000814757
-
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/