From: Michal Hocko <mhocko@kernel.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: threads-max observe limits
Date: Thu, 19 Sep 2019 09:59:11 +0200 [thread overview]
Message-ID: <20190919075911.GA15782@dhcp22.suse.cz> (raw)
In-Reply-To: <20190918071541.GB12770@dhcp22.suse.cz>
On Wed 18-09-19 09:15:41, Michal Hocko wrote:
> On Tue 17-09-19 12:26:18, Eric W. Biederman wrote:
[...]
> > b) Not being able to bump threads_max to the physical limit of
> > the machine is very clearly a regression.
>
> ... exactly this part. The changelog of the respective patch doesn't
> really exaplain why it is needed except of "it sounds like a good idea
> to be consistent".
Any take on this Heinrich? If there really is not strong reasoning about
the restricting user input then I will suggest reverting 16db3d3f1170
("kernel/sysctl.c: threads-max observe limits")
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-09-19 7:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 10:03 threads-max observe limits Michal Hocko
2019-09-17 15:28 ` Heinrich Schuchardt
2019-09-17 15:38 ` Michal Hocko
2019-09-17 17:26 ` Eric W. Biederman
2019-09-18 7:15 ` Michal Hocko
2019-09-19 7:59 ` Michal Hocko [this message]
2019-09-19 19:38 ` Andrew Morton
2019-09-19 19:33 ` Eric W. Biederman
2019-09-22 6:58 ` Michal Hocko
2019-09-22 15:31 ` Heinrich Schuchardt
2019-09-22 21:40 ` Eric W. Biederman
2019-09-22 21:24 ` Eric W. Biederman
2019-09-23 8:08 ` Michal Hocko
2019-09-23 21:23 ` Eric W. Biederman
2019-09-24 8:48 ` Michal Hocko
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=20190919075911.GA15782@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xypron.glpk@gmx.de \
/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