linux-kernel - Re: vxfs_readdir locking incorrect: add lock_kernel() or remove unlock

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] [day] [month] [year] [list]

Message-Id: <200607252225.k6PMP4Sf029794@turing-police.cc.vt.edu>
Date:	Tue, 25 Jul 2006 18:25:04 -0400
From:	Valdis.Kletnieks@...edu
To:	Andrew Morton <akpm@...l.org>
Cc:	Josh Triplett <josht@...ibm.com>, linux-kernel@...r.kernel.org,
	hch@...radead.org
Subject: Re: vxfs_readdir locking incorrect: add lock_kernel() or remove unlock_kernel()?

On Mon, 24 Jul 2006 17:20:40 PDT, Andrew Morton said:
> That would appear to imply that nobody has used freevxfs in four years.

Given that...

> I don't see anything in there which needs the locking, apart from perhaps
> f_pos updates.  But it's probably best to add the lock_kernel() - this is a
> bugfixing exercise, not a remove-BKL-from-freevxfs exercise.

Should we consider a remove-freevxfs-from-kernel exercise?

Content of type "application/pgp-signature" skipped