[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJ9+t272-pB914gYochtzX56yUPTd0Vf_=xfkjuOTpRfg@mail.gmail.com>
Date: Tue, 20 Jun 2017 17:23:16 -0700
From: Kees Cook <keescook@...omium.org>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Jessica Yu <jeyu@...hat.com>, Shuah Khan <shuah@...nel.org>,
Rusty Russell <rusty@...tcorp.com.au>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Jonathan Corbet <corbet@....net>,
Josh Triplett <josh@...htriplett.org>, martin.wilck@...e.com,
Michal Marek <mmarek@...e.com>, Petr Mladek <pmladek@...e.com>,
hare <hare@...e.com>, rwright@....com,
Jeff Mahoney <jeffm@...e.com>, David Sterba <DSterba@...e.com>,
Filipe Manana <fdmanana@...e.com>, NeilBrown <neilb@...e.com>,
Guenter Roeck <linux@...ck-us.net>, rgoldwyn@...e.com,
Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>,
Heinrich Schuchardt <xypron.glpk@....de>,
Aaron Tomlin <atomlin@...hat.com>,
Miroslav Benes <mbenes@...e.cz>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Dan Williams <dan.j.williams@...el.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
Ingo Molnar <mingo@...hat.com>,
Alan Cox <alan@...ux.intel.com>, "Ted Ts'o" <tytso@....edu>,
Greg KH <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kselftest@...r.kernel.org,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/4] kmod: help make deterministic
On Tue, Jun 20, 2017 at 1:56 PM, Luis R. Rodriguez <mcgrof@...nel.org> wrote:
> On Fri, May 26, 2017 at 02:12:24PM -0700, Luis R. Rodriguez wrote:
>> This v3 nukes the proc sysctl interface in favor for just letting userspace
>> just check kernel revision. Prior to whenever this is merged userspace should
>> try to avoid hammering more than 50 kmod threads as they can fail and it'd
>> get -ENOMEM.
>>
>> We do away with the old heuristics on assuming you could end up with
>> less than max_threads/2 < 50 threads as Dmitry notes this would mean having
>> a system with 16 MiB of RAM with modules enabled. It simplifies our patch
>> "kmod: reduce atomic operations on kmod_concurrent" considerbly.
>>
>> Since the sysctl interface is gone, this no longer depends on any
>> other patches, the series is independent. As usual the series is
>> available on my linux-next 20170526-kmod-only branch which is based
>> on next-20170526.
>>
>> [0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/log/?h=20170526-kmod-only
>>
>> Luis
>>
>> Luis R. Rodriguez (4):
>> module: use list_for_each_entry_rcu() on find_module_all()
>> kmod: reduce atomic operations on kmod_concurrent and simplify
>> kmod: add test driver to stress test the module loader
>> kmod: throttle kmod thread limit
>
> About a month now with no further nitpicks. What tree should these changes
> go through if there are no issues? Andrew's, Jessica's ?
Seems like going through Jessica's would make the most sense?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists