From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Mahesh Salgaonkar <mahesh@linux.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Ganesh Goudar <ganeshgr@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] powerpc: Avoid nmi_enter/nmi_exit in real mode interrupt.
Date: Sun, 27 Feb 2022 18:38:40 +0000 [thread overview]
Message-ID: <04d111d4-1764-e164-a995-9de591e9554d@csgroup.eu> (raw)
In-Reply-To: <164578465828.74956.6065296024817333750.stgit@jupiter>
Le 25/02/2022 à 11:24, Mahesh Salgaonkar a écrit :
> nmi_enter()/nmi_exit() touches per cpu variables which can lead to kernel
> crash when invoked during real mode interrupt handling (e.g. early HMI/MCE
> interrupt handler) if percpu allocation comes from vmalloc area.
>
> Early HMI/MCE handlers are called through DEFINE_INTERRUPT_HANDLER_NMI()
> wrapper which invokes nmi_enter/nmi_exit calls. We don't see any issue when
> percpu allocation is from the embedded first chunk. However with
> CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK enabled there are chances where percpu
> allocation can come from the vmalloc area.
>
> With kernel command line "percpu_alloc=page" we can force percpu allocation
> to come from vmalloc area and can see kernel crash in machine_check_early:
>
> [ 1.215714] NIP [c000000000e49eb4] rcu_nmi_enter+0x24/0x110
> [ 1.215717] LR [c0000000000461a0] machine_check_early+0xf0/0x2c0
> [ 1.215719] --- interrupt: 200
> [ 1.215720] [c000000fffd73180] [0000000000000000] 0x0 (unreliable)
> [ 1.215722] [c000000fffd731b0] [0000000000000000] 0x0
> [ 1.215724] [c000000fffd73210] [c000000000008364] machine_check_early_common+0x134/0x1f8
>
> Fix this by avoiding use of nmi_enter()/nmi_exit() in real mode if percpu
> first chunk is not embedded.
>
> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.ibm.com>
> ---
> arch/powerpc/include/asm/interrupt.h | 15 +++++++++++++++
> arch/powerpc/include/asm/percpu.h | 2 ++
> arch/powerpc/kernel/setup_64.c | 3 +++
> 3 files changed, 20 insertions(+)
In file included from /linux/arch/powerpc/kernel/irq.c:57:0:
/linux/arch/powerpc/include/asm/interrupt.h: In function
'interrupt_nmi_enter_prepare':
/linux/arch/powerpc/include/asm/interrupt.h:337:109: error:
'__percpu_embed_first_chunk' undeclared (first use in this function)
/linux/arch/powerpc/include/asm/interrupt.h:337:109: note: each
undeclared identifier is reported only once for each function it appears in
In file included from /linux/arch/powerpc/kernel/irq.c:57:0:
/linux/arch/powerpc/include/asm/interrupt.h: In function
'interrupt_nmi_exit_prepare':
/linux/arch/powerpc/include/asm/interrupt.h:353:109: error:
'__percpu_embed_first_chunk' undeclared (first use in this function)
In file included from /linux/arch/powerpc/kernel/irq.c:57:0:
/linux/arch/powerpc/include/asm/interrupt.h:366:1: error: label at end
of compound statement
skip_nmi_exit:
^
/linux/scripts/Makefile.build:288: recipe for target
'arch/powerpc/kernel/irq.o' failed
make[3]: *** [arch/powerpc/kernel/irq.o] Error 1
prev parent reply other threads:[~2022-02-27 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 10:24 [PATCH] powerpc: Avoid nmi_enter/nmi_exit in real mode interrupt Mahesh Salgaonkar
2022-02-25 13:54 ` Christophe Leroy
2022-02-27 18:38 ` Christophe Leroy [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=04d111d4-1764-e164-a995-9de591e9554d@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=aneesh.kumar@linux.ibm.com \
--cc=ganeshgr@linux.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=npiggin@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