[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1503021008400.9089@pobox.suse.cz>
Date: Mon, 2 Mar 2015 10:13:05 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Peter Zijlstra <peterz@...radead.org>
cc: mingo@...nel.org, rusty@...tcorp.com.au,
mathieu.desnoyers@...icios.com, oleg@...hat.com,
paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
andi@...stfloor.org, rostedt@...dmis.org, tglx@...utronix.de,
Seth Jennings <sjenning@...hat.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Miroslav Benes <mbenes@...e.cz>, Petr Mladek <pmladek@...e.cz>
Subject: Re: [RFC][PATCH 1/9] klp: Fix obvious RCU fail
On Mon, 2 Mar 2015, Peter Zijlstra wrote:
> > Acked-by: Jiri Kosina <jkosina@...e.cz>
> >
> > I guess you'll be taking this together with the series, so I am not
> > applying it.
>
> Feel free to take it; this series might take a wee while longer to
> mature.
OK, thanks.
> That said; I do have a follow up question on that code. So now you've
> successfully obtained an address in module space; but the moment you
> release that RCU-sched lock, the module can be gone.
>
> How does the whole live patching stuff deal with module removal during
> patching?
We have a module notifier that serializes using klp_mutex with the
patching. Do you see a problem there?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists