[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165279381181.2978864.3665903579432057917.b4-ty@kernel.org>
Date: Tue, 17 May 2022 15:04:44 +0100
From: Will Deacon <will@...nel.org>
To: Elliot Berman <quic_eberman@...cinc.com>,
Catalin Marinas <catalin.marinas@....com>,
Alexey Makhalov <amakhalov@...are.com>,
Juergen Gross <jgross@...e.com>,
"Srivatsa S. Bhat (VMware)" <srivatsa@...il.mit.edu>
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
Prakruthi Deepak Heragu <quic_pheragu@...cinc.com>,
linux-kernel@...r.kernel.org,
Murali Nalajala <quic_mnalajal@...cinc.com>,
virtualization@...ts.linux-foundation.org,
linux-arm-kernel@...ts.infradead.org, x86@...nel.org
Subject: Re: [PATCH v3] arm64: paravirt: Use RCU read locks to guard stolen_time
On Fri, 13 May 2022 10:46:54 -0700, Elliot Berman wrote:
> From: Prakruthi Deepak Heragu <quic_pheragu@...cinc.com>
>
> During hotplug, the stolen time data structure is unmapped and memset.
> There is a possibility of the timer IRQ being triggered before memset
> and stolen time is getting updated as part of this timer IRQ handler. This
> causes the below crash in timer handler -
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: paravirt: Use RCU read locks to guard stolen_time
https://git.kernel.org/arm64/c/19bef63f951e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists