linux-kernel - Re: [RFC] dealing with proc_ns_follow

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: <20141101183802.GR7996@ZenIV.linux.org.uk>
Date:	Sat, 1 Nov 2014 18:38:02 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	"Eric W.Biederman" <ebiederm@...ssion.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] dealing with proc_ns_follow_link() and "namespace" dentries

On Sat, Nov 01, 2014 at 11:23:34AM -0700, Eric W.Biederman wrote:

> >From your description I am concerned about using the letter combination nsfs.   I once used nsfd, and that was so close to nfsd that Linus got confused, and hilarity ensued.   nsfs isn't quite as bad but the abbreviation still seems close enough to nfs that confusion could result.

Well, yes, but... the only non-static object in there with "nsfs" in the
name is nsfs_init().  As for the filename itself... any better suggestions
would be welcome, but it doesn't really mess the completion tree.

I've no strong preferences here - we might even move it into kernel/nsproxy.c.
In the latest variant it's ~160 lines...
--
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/