mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jun Miao <jun.miao@intel.com>
To: Marco Elver <elver@google.com>
Cc: <ryabinin.a.a@gmail.com>, Dmitry Vyukov <dvyukov@google.com>,
	<bigeasy@linutronix.de>, <qiang1.zhang@intel.com>,
	<peterz@infradead.org>, <akpm@linux-foundation.org>,
	<andreyknvl@gmail.com>, <ying.huang@intel.com>,
	<kasan-dev@googlegroups.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irq_work: Make irq_work_queue_on() NMI-safe again
Date: Wed, 27 Apr 2022 21:17:52 +0800	[thread overview]
Message-ID: <5a39e32f-c0d1-8cad-71a7-845417e51fa9@intel.com> (raw)
In-Reply-To: <CANpmjNNxOX12NcMjXJr3XWcoe6d+Dp74pR+2naVW0anwcYfmoQ@mail.gmail.com>


On 2022/4/27 20:26, Marco Elver wrote:
> On Wed, 27 Apr 2022 at 03:49, Jun Miao <jun.miao@intel.com> wrote:
>> Add  To/Cc : KASAN/MEM , since I only used the scripts/get_maintainer.pl
>> to irq_work.c file.
>>
>> Thanks
>> Jun Miao
>>
>>
>> On 2022/4/26 21:49, Jun Miao wrote:
>>> We should not put NMI unsafe code in irq_work_queue_on().
>>>
>>> The KASAN of kasan_record_aux_stack_noalloc() is not NMI safe. Because which
>>> will call the spinlock. While the irq_work_queue_on() is also very carefully
>>> carafted to be exactly that.
> "crafted"
>
>>> When unable CONFIG_SM or local CPU, the irq_work_queue_on() is even same to
> CONFIG_SM -> CONFIG_SMP
>
>>> irq_work_queue(). So delete KASAN instantly.
>>>
>>> Fixes: e2b5bcf9f5ba ("irq_work: record irq_work_queue() call stack")
>>> Suggested by: "Huang, Ying" <ying.huang@intel.com>
>>> Signed-off-by: Jun Miao <jun.miao@intel.com>
> I thought this had already been removed, but apparently there were 2
> places: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=156172a13ff0626d8e23276e741c7e2cb2f3b572
>
> Acked-by: Marco Elver <elver@google.com>

Sure, I also found this patch which is the same reason, maybe Peter Z 
forgot it. Let me make up a little.😉

Send V2 later.

Thanks
Jun Miao
>>> ---
>>>    kernel/irq_work.c | 3 ---
>>>    1 file changed, 3 deletions(-)
>>>
>>> diff --git a/kernel/irq_work.c b/kernel/irq_work.c
>>> index 7afa40fe5cc4..e7f48aa8d8af 100644
>>> --- a/kernel/irq_work.c
>>> +++ b/kernel/irq_work.c
>>> @@ -20,7 +20,6 @@
>>>    #include <linux/smp.h>
>>>    #include <linux/smpboot.h>
>>>    #include <asm/processor.h>
>>> -#include <linux/kasan.h>
>>>
>>>    static DEFINE_PER_CPU(struct llist_head, raised_list);
>>>    static DEFINE_PER_CPU(struct llist_head, lazy_list);
>>> @@ -137,8 +136,6 @@ bool irq_work_queue_on(struct irq_work *work, int cpu)
>>>        if (!irq_work_claim(work))
>>>                return false;
>>>
>>> -     kasan_record_aux_stack_noalloc(work);
>>> -
>>>        preempt_disable();
>>>        if (cpu != smp_processor_id()) {
>>>                /* Arch remote IPI send/receive backend aren't NMI safe */
>> --
>> You received this message because you are subscribed to the Google Groups "kasan-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to kasan-dev+unsubscribe@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/kasan-dev/9c951fe6-d354-5870-e91b-83d8346ac162%40intel.com.

  reply	other threads:[~2022-04-27 13:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 13:49 Jun Miao
2022-04-27  1:49 ` Jun Miao
2022-04-27 12:26   ` Marco Elver
2022-04-27 13:17     ` Jun Miao [this message]
2022-04-27 13:50 Jun Miao
2022-04-27 13:59 ` Jun Miao

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=5a39e32f-c0d1-8cad-71a7-845417e51fa9@intel.com \
    --to=jun.miao@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=qiang1.zhang@intel.com \
    --cc=ryabinin.a.a@gmail.com \
    --cc=ying.huang@intel.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®