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: <cfb295aa-0e4b-4185-875f-3745d2c5c01a@email.android.com>
Date:	Sat, 01 Nov 2014 11:23:34 -0700
From:	"Eric W.Biederman" <ebiederm@...ssion.com>
To:	Al Viro <viro@...IV.linux.org.uk>
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 November 1, 2014 8:06:20 AM PDT, Al Viro <viro@...IV.linux.org.uk> wrote:
>On Sat, Nov 01, 2014 at 08:38:04AM +0000, Al Viro wrote:
>> OK, interim branch (_completely_ untested, and there's quite a bit of
>> work remaining) is in vfs.git#nsfs.
>
>... except that what got pushed was completely buggered - the last
>changes
>not committed *and* include/linux/ns_common.h not git-add'ed at the
>very
>beginning.  Oh, well - it wasn't hard to reconstruct its history...
>
>Anyway, that much got fixed and pushed; sorry about the noise -
>shouldn't
>have posted before grabbing some sleep...

No worries.  I am effectively without internet access right from now until about the 3rd week in November as I move so I really can't look anyway.

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

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