[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180622143247.781028b1@gandalf.local.home>
Date: Fri, 22 Jun 2018 14:32:47 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Joel Fernandes <joel@...lfernandes.org>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Byungchul Park <max.byungchul.park@...il.com>,
Byungchul Park <byungchul.park@....com>,
jiangshanlai@...il.com, josh@...htriplett.org,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
linux-kernel@...r.kernel.org, kernel-team@....com, luto@...nel.org
Subject: Re: [RFC 2/2] rcu: Remove ->dynticks_nmi_nesting from struct
rcu_dynticks
On Fri, 22 Jun 2018 11:19:16 -0700
Joel Fernandes <joel@...lfernandes.org> wrote:
> Sure. So in a later thread you mentioned "usermode helpers". I took a closer
> look at that subsystem, and it seems you can execute usermode helpers from
> atomic sections with help of UMH_NO_WAIT flag.
>
> Then I checked where this flag is used and it turns out its from the
> mce_work_trigger function in x86/kernel/cpu/mcheck/dev-mcelog.c which can be
> called infact from an interrupt context (mce_notify_irq).
>
> Is this the usecase you remember causing this weird transitions to userspace?
But this case still looks like it uses work queues, it just doesn't
wait for the result.
I'll have to look at the code from what it looked like back in 2011, to
see if there was an actual issue here back then.
-- Steve
Powered by blists - more mailing lists