linux-kernel - Re: nfsd changes for 3.6

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: <20120731143600.GD27834@fieldses.org>
Date:	Tue, 31 Jul 2012 10:36:00 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-nfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
	matthew@....cx
Subject: Re: nfsd changes for 3.6

On Tue, Jul 31, 2012 at 10:29:48AM -0400, bfields wrote:
> Please pull nfsd (and some lockd and a couple locks/lease) changes from:

By the way, for a few years now I've been semi-regularly picking up
locks.c changes for my tree.  I wonder if I should be.

At the least we should probably remove this entry from MAINTAINERS?  And
by default I suppose that stuff reverts to Al, who rumor has it will
have a fair number of locks.c patches next time around.

Or I'm happy to claim to be maintainer of that file if somebody prefers,
it doesn't matter much to me.

--b.

diff --git a/MAINTAINERS b/MAINTAINERS
index 3e30a3a..305ac2c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2767,15 +2767,6 @@ F:	include/scsi/fc/
 F:	include/scsi/libfc.h
 F:	include/scsi/libfcoe.h
 
-FILE LOCKING (flock() and fcntl()/lockf())
-M:	Matthew Wilcox <matthew@....cx>
-L:	linux-fsdevel@...r.kernel.org
-S:	Maintained
-F:	include/linux/fcntl.h
-F:	include/linux/fs.h
-F:	fs/fcntl.c
-F:	fs/locks.c
-
 FILESYSTEMS (VFS and infrastructure)
 M:	Alexander Viro <viro@...iv.linux.org.uk>
 L:	linux-fsdevel@...r.kernel.org
--
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/