From: Thomas Gleixner <tglx@linutronix•de>
To: "Farber, Eliav" <farbere@amazon•com>,
"linux@armlinux•org.uk" <linux@armlinux•org.uk>,
"catalin.marinas@arm•com" <catalin.marinas@arm•com>,
"will@kernel•org" <will@kernel•org>,
"mpe@ellerman•id.au" <mpe@ellerman•id.au>,
"npiggin@gmail•com" <npiggin@gmail•com>,
"christophe.leroy@csgroup•eu" <christophe.leroy@csgroup•eu>,
"naveen@kernel•org" <naveen@kernel•org>,
"maddy@linux•ibm.com" <maddy@linux•ibm.com>,
"paul.walmsley@sifive•com" <paul.walmsley@sifive•com>,
"palmer@dabbelt•com" <palmer@dabbelt•com>,
"aou@eecs•berkeley.edu" <aou@eecs•berkeley.edu>,
"ebiederm@xmission•com" <ebiederm@xmission•com>,
"akpm@linux-foundation•org" <akpm@linux-foundation•org>,
"bhe@redhat•com" <bhe@redhat•com>,
"hbathini@linux•ibm.com" <hbathini@linux•ibm.com>,
"sourabhjain@linux•ibm.com" <sourabhjain@linux•ibm.com>,
"adityag@linux•ibm.com" <adityag@linux•ibm.com>,
"songshuaishuai@tinylab•org" <songshuaishuai@tinylab•org>,
"takakura@valinux•co.jp" <takakura@valinux•co.jp>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
"linux-riscv@lists•infradead.org"
<linux-riscv@lists•infradead.org>,
"kexec@lists•infradead.org" <kexec@lists•infradead.org>,
Marc Zyngier <maz@kernel•org>
Cc: "Chocron, Jonathan" <jonnyc@amazon•com>
Subject: RE: [PATCH v4 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation
Date: Sun, 01 Dec 2024 12:19:34 +0100 [thread overview]
Message-ID: <87frn7wszd.ffs@tglx> (raw)
In-Reply-To: <cd8809e379dc4dd089350ec2d1f8c210@amazon.com>
On Sat, Nov 30 2024 at 20:08, Eliav Farber wrote:
> On 11/29/2024 3:30 PM, Thomas Gleixner wrote:
>> Looking deeper. This function actually cannot be called from this
>> context. It does:
>>
>> irq_get_desc_buslock(irq, &flags, 0);
>>
>> which means for any interrupt which has an actual buslock implementation
>> it will end up in a sleepable function and deadlock in the worst case.
>>
>> Marc?
> I will wait for Marc's response regarding this issue.
> Regardless, if any changes are required, I believe it would be better
> to address them in a separate patch, as this behavior existed before my
> modification.
Correct.
next prev parent reply other threads:[~2024-12-01 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 20:08 [PATCH v4 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation Farber, Eliav
2024-12-01 11:19 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-29 11:31 [PATCH v4 0/2] Improve interrupt handling during machine kexec Eliav Farber
2024-11-29 11:31 ` [PATCH v4 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation Eliav Farber
2024-11-29 13:30 ` Thomas Gleixner
2024-11-29 15:31 ` kernel test robot
2024-11-29 15:53 ` kernel test robot
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=87frn7wszd.ffs@tglx \
--to=tglx@linutronix$(echo .)de \
--cc=adityag@linux$(echo .)ibm.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=aou@eecs$(echo .)berkeley.edu \
--cc=bhe@redhat$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=ebiederm@xmission$(echo .)com \
--cc=farbere@amazon$(echo .)com \
--cc=hbathini@linux$(echo .)ibm.com \
--cc=jonnyc@amazon$(echo .)com \
--cc=kexec@lists$(echo .)infradead.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=maz@kernel$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=naveen@kernel$(echo .)org \
--cc=npiggin@gmail$(echo .)com \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=songshuaishuai@tinylab$(echo .)org \
--cc=sourabhjain@linux$(echo .)ibm.com \
--cc=takakura@valinux$(echo .)co.jp \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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