From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: 杨男子 <nzyang@stu.xidian.edu.cn>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
security@kernel.org
Subject: Re: Report Bug to Linux File System about fs/devpts
Date: Sun, 5 Sep 2021 21:36:56 -0400 [thread overview]
Message-ID: <YTVwuH4sxcGqT2BP@mit.edu> (raw)
In-Reply-To: <YTT8QQqQ2n63OVSP@kroah.com>
On Sun, Sep 05, 2021 at 07:20:01PM +0200, Greg KH wrote:
> If you are concerned about this, please restrict the kernel.pty.max
> value to be much lower.
The kernel.pty.max value specifies the global maximum limit. So I
believe the point solution to *this* particular container resource
limit is to mount separate instances of /dev/pts in each container
chroot with the mount option max=NUM, instead of bind-mounting the
top-level /dev/pts into each container chroot.
And <whack> we can use the rubber mallet to hit one more mole in the
whack-a-mole game. :-)
Or you can just assume that all of the containers are cooperatively
trying to share the OS resources, and if there is a malicious
container, it can be handled out-of-band by non-technical means (e.g.,
by having the Site Reliability Engineer tracking down owner of said
malicious container, and then talking to their manager to tell them
not to do that particular anti-social thing, docking the owner's
social credit account, etc.).
- Ted
next prev parent reply other threads:[~2021-09-06 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 6:31 Report Bug to Linux File System about fs/devpts 杨男子
2021-09-05 17:20 ` Greg KH
2021-09-06 1:36 ` Theodore Ts'o [this message]
2021-09-06 9:01 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YTVwuH4sxcGqT2BP@mit.edu \
--to=tytso@mit.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nzyang@stu.xidian.edu.cn \
--cc=security@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).