linux-kernel - Re: [PATCH] proc: reset mount options after the last procfs umount

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: <20120331152039.GA4674@albatros>
Date:	Sat, 31 Mar 2012 19:20:39 +0400
From:	Vasiliy Kulikov <segoon@...nwall.com>
To:	Arkadiusz Miśkiewicz <a.miskiewicz@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, Valdis.Kletnieks@...edu,
	linux-kernel@...r.kernel.org, Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [PATCH] proc: reset mount options after the last procfs umount

On Sat, Mar 31, 2012 at 16:19 +0200, Arkadiusz Miśkiewicz wrote:
> "after all procs are umounted". For me such way is fine but still can suprise 
> people.
> 
> Anyway - what's the problem with implementing support for separate options for 
> each mount point?

Well, IMHO multiple procs in one pid namespace is a very strange system
configuration.  I didn't see such installations.  Why does anybody need it?

Thanks,

-- 
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
--
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/