linux-kernel - Re: [PATCH] fs/locks.c: prepare for BKL removal

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]

Date:	Thu, 23 Sep 2010 08:40:11 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Sage Weil <sage@...dream.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org,
	Matthew Wilcox <willy@...ux.intel.com>,
	Christoph Hellwig <hch@....de>,
	Trond Myklebust <trond.myklebust@....uio.no>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Miklos Szeredi <mszeredi@...e.cz>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>, John Kacur <jkacur@...hat.com>,
	linux-fsdevel@...r.kernel.org, gregf@...newdream.net
Subject: Re: [PATCH] fs/locks.c: prepare for BKL removal

On Thursday 23 September 2010 05:42:49 Sage Weil wrote:
> Okay, the lock/unlock_flocks() stubs on in Linus' tree now, and the Ceph 
> for-next branch is rebased and updated to fix the memory allocations and 
> switch to the new interface.

Ok. I'll put the patches for the other stuff (everything but ceph and lockd)
in my bkl/vfs branch then.

> Unfortunately you still need to #include smp_lock.h for now since the 
> stubs are just #defines, so we'll need to remember to clean that up later.

Don't worry about that. We have a few of those leftover ones, so we can
do a single patch removing them all before one day removing the header
file itself.

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