From: Oleg Nesterov <oleg@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andy Lutomirski <tipbot@zytor.com>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Pratyush Anand <panand@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH tip/x86/asm] uprobes: __create_xol_area() must nullify xol_mapping.fault
Date: Mon, 29 Feb 2016 16:51:14 +0100 [thread overview]
Message-ID: <20160229155114.GA1922@redhat.com> (raw)
In-Reply-To: <20160229114210.GK6356@twins.programming.kicks-ass.net>
On 02/29, Peter Zijlstra wrote:
>
> On Sat, Feb 27, 2016 at 11:11:28PM +0100, Oleg Nesterov wrote:
> > --- a/kernel/events/uprobes.c
> > +++ b/kernel/events/uprobes.c
> > @@ -1178,6 +1178,7 @@ static struct xol_area *__create_xol_area(unsigned long vaddr)
> > goto free_area;
> >
> > area->xol_mapping.name = "[uprobes]";
> > + area->xol_mapping.fault = NULL;
> > area->xol_mapping.pages = area->pages;
>
> Would not something like:
>
> area->xol_mapping = (struct vm_special_mapping){
> .name = "[uprobes]",
> .pages = area->pages,
> };
>
> Be a more robust approach? That way, if someone adds more fields, they
> at least get initialized (to 0).
OK, agreed...
Do you want me to send v2? Or incremental patch because this one is already in
-tip tree.
Or do nothing unless you feel strongly about it. area->xol_mapping should go away,
but we need a simple preparation in mm/mmap.c.
Oleg.
next prev parent reply other threads:[~2016-02-29 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 22:11 [PATCH tip/x86/asm] uprobes: __create_xol_area() must nullify xol_mapping.fault Oleg Nesterov
2016-02-29 11:02 ` [tip:x86/asm] " tip-bot for Oleg Nesterov
2016-02-29 11:42 ` [PATCH tip/x86/asm] " Peter Zijlstra
2016-02-29 15:51 ` Oleg Nesterov [this message]
2016-02-29 16:14 ` Peter Zijlstra
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=20160229155114.GA1922@redhat.com \
--to=oleg@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=panand@redhat.com \
--cc=peterz@infradead.org \
--cc=tipbot@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.