linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: david@redhat.com, akpm@linux-foundation.org,
	Jianyong Wu <jianyong.wu@arm.com>,
	anshuman.khandual@arm.com, ardb@kernel.org,
	catalin.marinas@arm.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	nd@arm.com, justin.he@arm.com, gshan@redhat.com,
	quic_qiancai@quicinc.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PATCH v4] arm64/mm: avoid fixmap race condition when create pud mapping
Date: Tue, 15 Feb 2022 23:18:30 +0000	[thread overview]
Message-ID: <164493953489.1197740.9545575140952933000.b4-ty@kernel.org> (raw)
In-Reply-To: <20220201114400.56885-1-jianyong.wu@arm.com>

On Tue, 1 Feb 2022 19:44:00 +0800, Jianyong Wu wrote:
> The 'fixmap' is a global resource and is used recursively by
> create pud mapping(), leading to a potential race condition in the
> presence of a concurrent call to alloc_init_pud():
> 
> kernel_init thread                          virtio-mem workqueue thread
> ==================                          ===========================
> 
> [...]

Applied to arm64 (for-next/mm), thanks!

[1/1] arm64/mm: avoid fixmap race condition when create pud mapping
      https://git.kernel.org/arm64/c/ee017ee35350

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

      parent reply	other threads:[~2022-02-15 23:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 11:44 [PATCH] [PATCH v4] arm64/mm: avoid fixmap race condition when create pud mapping Jianyong Wu
2022-02-04 18:44 ` Catalin Marinas
2022-02-15 23:18 ` Will Deacon [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=164493953489.1197740.9545575140952933000.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=gshan@redhat.com \
    --cc=jianyong.wu@arm.com \
    --cc=justin.he@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nd@arm.com \
    --cc=quic_qiancai@quicinc.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;
as well as URLs for NNTP newsgroup(s).