linux-kernel - Re: [PATCH] [1/11] Remove BKL from remote

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

Message-ID: <483191AA.9030202@firstfloor.org>
Date:	Mon, 19 May 2008 16:41:46 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Trond Myklebust <Trond.Myklebust@...app.com>
CC:	swhiteho@...hat.com, sfrench@...ba.org, vandrove@...cvut.cz,
	corbet@....net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [1/11] Remove BKL from remote_llseek


> The one case in nfs_file_llseek() where we might care is the call to
> nfs_revalidate_file_size() ('cos I still haven't finished auditing BKL
> dependencies in the inode attributes). However that case should already
> be covered without introducing any new lock_kernel/unlock_kernel calls
> since __nfs_revalidate_inode() already grabs the BKL.

Thanks. I'll keep it for now with the explicit lock_kernel() and when you're 
finished  your audit and the patches are in before you can just remove them 
yourself. I guess that's the best way to handle it.

-Andi


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