From: Peter Zijlstra <peterz@infradead.org>
To: Jun Miao <jun.miao@intel.com>
Cc: elver@google.com, dvyukov@google.com, ryabinin.a.a@gmail.com,
bigeasy@linutronix.de, qiang1.zhang@intel.com,
andreyknvl@gmail.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH v2] irq_work: Make irq_work_queue_on() NMI-safe again
Date: Thu, 28 Apr 2022 11:24:45 +0200 [thread overview]
Message-ID: <YmpdXfJswI9rlG3w@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220427135549.20901-1-jun.miao@intel.com>
On Wed, Apr 27, 2022 at 09:55:49PM +0800, Jun Miao wrote:
> We should not put NMI unsafe code in irq_work_queue_on().
Why not, irq_work_queue_on() is not NMI safe. Only irq_work_queue() is.
prev parent reply other threads:[~2022-04-28 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:55 [PATCH v2] irq_work: Make irq_work_queue_on() NMI-safe again Jun Miao
2022-04-28 9:24 ` Peter Zijlstra [this message]
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=YmpdXfJswI9rlG3w@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=jun.miao@intel.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=ryabinin.a.a@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