From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D6856C3A5A6 for ; Thu, 19 Sep 2019 07:59:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A9DBA207FC for ; Thu, 19 Sep 2019 07:59:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568879954; bh=+CjimZzWdqd+uh7Kju/20jAK+vnt3mZ1bl0Yfcg/s+w=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Er9iUT5+Oh6kvAw8c08akFjKiMqJ7xL13kjoRUDQQakzEHjTNEnR7ScrDyb8L4Ar/ d3Tg5D4Ji4pBnrjOPTTje3iedAQmvaAjDKUqeMxjOf4VHBqB15cl6+F/WdUOWNsi0y Ma1MTvuSIO6OkdO+B8rsvHc/CZWtB2obvEtI1MAE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388091AbfISH7N (ORCPT ); Thu, 19 Sep 2019 03:59:13 -0400 Received: from mx2.suse.de ([195.135.220.15]:47366 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727033AbfISH7N (ORCPT ); Thu, 19 Sep 2019 03:59:13 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id BF259AD2B; Thu, 19 Sep 2019 07:59:11 +0000 (UTC) Date: Thu, 19 Sep 2019 09:59:11 +0200 From: Michal Hocko To: Heinrich Schuchardt Cc: "Eric W. Biederman" , Andrew Morton , LKML Subject: Re: threads-max observe limits Message-ID: <20190919075911.GA15782@dhcp22.suse.cz> References: <20190917100350.GB1872@dhcp22.suse.cz> <38349607-b09c-fa61-ccbb-20bee9f282a3@gmx.de> <20190917153830.GE1872@dhcp22.suse.cz> <87ftku96md.fsf@x220.int.ebiederm.org> <20190918071541.GB12770@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190918071541.GB12770@dhcp22.suse.cz> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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