From: Michal Hocko <mhocko@kernel.org>
To: Hoeun Ryu <hoeun.ryu@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v3] fork: free vmapped stacks in cache when cpus are offline
Date: Fri, 10 Feb 2017 13:05:24 +0100 [thread overview]
Message-ID: <20170210120524.GI10893@dhcp22.suse.cz> (raw)
In-Reply-To: <1486715554-12772-1-git-send-email-hoeun.ryu@gmail.com>
On Fri 10-02-17 17:32:07, Hoeun Ryu wrote:
[...]
> +static int free_vm_stack_cache(unsigned int cpu)
> +{
> + struct vm_struct **cached_vm_stacks = per_cpu_ptr(cached_stacks, cpu);
> + int i;
> +
> + for (i = 0; i < NR_CACHED_STACKS; i++) {
> + struct vm_struct **vm_stack = &cached_vm_stacks[i];
> +
> + if (*vm_stack == NULL)
> + continue;
> +
> + vfree((*vm_stack)->addr);
> + *vm_stack = NULL;
this seems more obscure than necessary. Probably a matter of taste but I
would find the following easier to read
struct vm_struct *vm_stack = cached_vm_stacks[i];
if (!vm_stack)
continue;
vfree(vm_stack);
cached_vm_stacks[i] = NULL;
> + }
> +
> + return 0;
> +}
> #endif
>
> static unsigned long *alloc_thread_stack_node(struct task_struct *tsk, int node)
> @@ -456,6 +474,11 @@ void __init fork_init(void)
> for (i = 0; i < UCOUNT_COUNTS; i++) {
> init_user_ns.ucount_max[i] = max_threads/2;
> }
> +
> +#ifdef CONFIG_VMAP_STACK
> + cpuhp_setup_state(CPUHP_AP_ONLINE_DYN, "vm_stack_cache",
> + NULL, free_vm_stack_cache);
> +#endif
I am not familiar the new hotplug infrastructure so I might be missing
something. CPUHP_AP_ONLINE_DYN will allocate a state which is has only
30 slots available. The name also suggests this will be called on an
online event. Why doesn't this have its own state like other users. The
name should also reflect offline event CPUHP_STACK_CACHE_DEAD or
something like that.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-02-10 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 8:32 Hoeun Ryu
2017-02-10 12:05 ` Michal Hocko [this message]
2017-02-10 14:31 ` Hoeun Ryu
2017-02-10 14:41 ` Michal Hocko
2017-02-10 15:00 ` Hoeun Ryu
2017-02-10 15:34 ` Thomas Gleixner
2017-02-10 15:32 ` Thomas Gleixner
2017-02-10 16:42 ` Hoeun Ryu
2017-02-10 17:51 ` Thomas Gleixner
2017-02-10 23:33 ` Hoeun Ryu
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=20170210120524.GI10893@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--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=mingo@kernel.org \
--cc=oleg@redhat.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
all inboxes | Powered by JetHome®