[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8737qhdknk.fsf@x220.int.ebiederm.org>
Date: Tue, 19 Apr 2016 22:27:43 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>, security@...ian.org,
"security\@kernel.org" <security@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>,
"security\@ubuntu.com \>\> security" <security@...ntu.com>,
Peter Hurley <peter@...leysoftware.com>,
Serge Hallyn <serge.hallyn@...ntu.com>,
Willy Tarreau <w@....eu>,
Aurelien Jarno <aurelien@...el32.net>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Jann Horn <jann@...jh.net>, Greg KH <greg@...ah.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jiri Slaby <jslaby@...e.com>, Florian Weimer <fw@...eb.enyo.de>
Subject: Re: [PATCH 14/16] vfs: Implement mount_super_once
"H. Peter Anvin" <hpa@...or.com> writes:
> On April 19, 2016 12:25:03 PM PDT, "H. Peter Anvin" <hpa@...or.com> wrote:
>>
>>Perhaps a (privileged) option to exempt from the global limit, then.
>>Something we can implement if asked for.
>>
>>However, I wouldn't be 100% that the reserved pool isn't used. Someone
>>added it presumably for a reason. An administrator could say it and
>>we'd have no idea.
>
> ... and if I personally was running a container-hosting system, I
> would *absolutely* set it to make sure the administrator could not get
> locked out.
That is likely easier done by setting:
echo RIDICULOUSLY_LARGE_NUMBER > /proc/sys/kernel/pty/max
All I am certain about at this point is that no one cares on a day to
day basis or in any kind of ordinary scenario so this is something that
we can get away with changing.
But yes I would not be surprised if we have to come back and implement
something like your suggested extra mount option for devpts, so some
specified instances can dip into the reserved pool.
Eric
Powered by blists - more mailing lists