All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Elliot Berman <quic_eberman@quicinc.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Alexey Makhalov <amakhalov@vmware.com>,
	Juergen Gross <jgross@suse.com>,
	"Srivatsa S. Bhat (VMware)" <srivatsa@csail.mit.edu>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>,
	linux-kernel@vger.kernel.org,
	Murali Nalajala <quic_mnalajal@quicinc.com>,
	virtualization@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org, x86@kernel.org
Subject: Re: [PATCH v3] arm64: paravirt: Use RCU read locks to guard stolen_time
Date: Tue, 17 May 2022 15:04:44 +0100	[thread overview]
Message-ID: <165279381181.2978864.3665903579432057917.b4-ty@kernel.org> (raw)
In-Reply-To: <20220513174654.362169-1-quic_eberman@quicinc.com>

On Fri, 13 May 2022 10:46:54 -0700, Elliot Berman wrote:
> From: Prakruthi Deepak Heragu <quic_pheragu@quicinc.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

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Elliot Berman <quic_eberman@quicinc.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Alexey Makhalov <amakhalov@vmware.com>,
	Juergen Gross <jgross@suse.com>,
	"Srivatsa S. Bhat (VMware)" <srivatsa@csail.mit.edu>
Cc: Murali Nalajala <quic_mnalajal@quicinc.com>,
	kernel-team@android.com, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] arm64: paravirt: Use RCU read locks to guard stolen_time
Date: Tue, 17 May 2022 15:04:44 +0100	[thread overview]
Message-ID: <165279381181.2978864.3665903579432057917.b4-ty@kernel.org> (raw)
In-Reply-To: <20220513174654.362169-1-quic_eberman@quicinc.com>

On Fri, 13 May 2022 10:46:54 -0700, Elliot Berman wrote:
> From: Prakruthi Deepak Heragu <quic_pheragu@quicinc.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
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Elliot Berman <quic_eberman@quicinc.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Alexey Makhalov <amakhalov@vmware.com>,
	Juergen Gross <jgross@suse.com>,
	"Srivatsa S. Bhat (VMware)" <srivatsa@csail.mit.edu>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>,
	linux-kernel@vger.kernel.org,
	Murali Nalajala <quic_mnalajal@quicinc.com>,
	virtualization@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org, x86@kernel.org
Subject: Re: [PATCH v3] arm64: paravirt: Use RCU read locks to guard stolen_time
Date: Tue, 17 May 2022 15:04:44 +0100	[thread overview]
Message-ID: <165279381181.2978864.3665903579432057917.b4-ty@kernel.org> (raw)
In-Reply-To: <20220513174654.362169-1-quic_eberman@quicinc.com>

On Fri, 13 May 2022 10:46:54 -0700, Elliot Berman wrote:
> From: Prakruthi Deepak Heragu <quic_pheragu@quicinc.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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-05-17 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 17:46 [PATCH v3] arm64: paravirt: Use RCU read locks to guard stolen_time Elliot Berman
2022-05-13 17:46 ` Elliot Berman
2022-05-13 23:32 ` Srivatsa S. Bhat
2022-05-13 23:32   ` Srivatsa S. Bhat
2022-05-13 23:32   ` Srivatsa S. Bhat
2022-05-17  8:54   ` Will Deacon
2022-05-17  8:54     ` Will Deacon
2022-05-17  8:54     ` Will Deacon
2022-05-17 16:48     ` Srivatsa S. Bhat
2022-05-17 16:48       ` Srivatsa S. Bhat
2022-05-17 16:48       ` Srivatsa S. Bhat
2022-05-17 14:04 ` Will Deacon [this message]
2022-05-17 14:04   ` Will Deacon
2022-05-17 14:04   ` Will Deacon

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=165279381181.2978864.3665903579432057917.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=amakhalov@vmware.com \
    --cc=catalin.marinas@arm.com \
    --cc=jgross@suse.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_eberman@quicinc.com \
    --cc=quic_mnalajal@quicinc.com \
    --cc=quic_pheragu@quicinc.com \
    --cc=srivatsa@csail.mit.edu \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.