From: Eric Biggers <ebiggers3@gmail.com>
To: Hoeun Ryu <hoeun.ryu@gmail.com>
Cc: "Kees Cook" <keescook@chromium.org>,
"Michal Marek" <mmarek@suse.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Emese Revfy" <re.emese@gmail.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Michal Hocko" <mhocko@suse.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Mateusz Guzik" <mguzik@redhat.com>,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] [PATCH v2 2/2] fork: make number of cached stacks (vmapped) configurable using Kbuild
Date: Wed, 8 Feb 2017 20:26:29 -0800 [thread overview]
Message-ID: <20170209042629.GB4311@zzz> (raw)
In-Reply-To: <1486613040-30555-2-git-send-email-hoeun.ryu@gmail.com>
On Thu, Feb 09, 2017 at 01:03:47PM +0900, Hoeun Ryu wrote:
> +config NR_VMAP_STACK_CACHE
> + int "Number of cached stacks"
> + default "2"
> + depends on VMAP_STACK
> + help
> + This determines how many stacks can be cached for virtually
> + mapped kernel stacks.
> +
Can you explain in the help text under what circumstances someone should change
this, and to what value? As-is, it seems like somewhat of a useless config
option which no one will ever change.
- Eric
next prev parent reply other threads:[~2017-02-09 4:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 4:03 [PATCH v2 1/2] fork: free vmapped stacks in cache when cpus are offline Hoeun Ryu
2017-02-09 4:03 ` [PATCH v2 2/2] fork: make number of cached stacks (vmapped) configurable using Kbuild Hoeun Ryu
2017-02-09 4:26 ` Eric Biggers [this message]
2017-02-09 8:40 ` Michal Hocko
2017-02-09 13:36 ` Hoeun Ryu
2017-02-09 4:22 ` [kernel-hardening] [PATCH v2 1/2] fork: free vmapped stacks in cache when cpus are offline Eric Biggers
2017-02-09 13:35 ` Hoeun Ryu
2017-02-09 7:28 ` kbuild test robot
2017-02-09 8:01 ` kbuild test robot
2017-02-09 8:38 ` Michal Hocko
2017-02-09 13:36 ` Hoeun Ryu
2017-02-09 10:26 ` kbuild test robot
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=20170209042629.GB4311@zzz \
--to=ebiggers3@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hoeun.ryu@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mguzik@redhat.com \
--cc=mhocko@suse.com \
--cc=mic@digikod.net \
--cc=mingo@kernel.org \
--cc=mmarek@suse.com \
--cc=npiggin@gmail.com \
--cc=re.emese@gmail.com \
/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).