From: Will Deacon <will@kernel.org>
To: anshuman.khandual@arm.com, catalin.marinas@arm.com,
Jianyong Wu <jianyong.wu@arm.com>,
akpm@linux-foundation.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, gshan@redhat.com,
david@redhat.com, justin.he@arm.com, ardb@kernel.org, nd@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64/mm: avoid fixmap race condition when create pud mapping
Date: Mon, 13 Dec 2021 16:42:44 +0000 [thread overview]
Message-ID: <163941094777.2464379.2692109101400876104.b4-ty@kernel.org> (raw)
In-Reply-To: <20211210095432.51798-1-jianyong.wu@arm.com>
On Fri, 10 Dec 2021 17:54:32 +0800, Jianyong Wu wrote:
> fixmap is a global resource and is used recursively in create pud mapping.
> It may lead to race condition when alloc_init_pud is called concurrently.
>
> Fox example:
> alloc_init_pud is called when kernel_init. If memory hotplug
> thread, which will also call alloc_init_pud, happens during
> kernel_init, the race for fixmap occurs.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/mm: avoid fixmap race condition when create pud mapping
https://git.kernel.org/arm64/c/a6a6b9aa34e5
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2021-12-13 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 9:54 [PATCH v2] arm64/mm: avoid fixmap race condition when create pud mapping Jianyong Wu
2021-12-10 11:22 ` Catalin Marinas
2021-12-13 5:24 ` Jianyong Wu
2021-12-13 6:56 ` Anshuman Khandual
2021-12-13 7:27 ` Jianyong Wu
2021-12-13 7:37 ` David Hildenbrand
2021-12-13 9:57 ` Catalin Marinas
2021-12-13 10:16 ` Anshuman Khandual
2021-12-13 10:35 ` Ard Biesheuvel
2021-12-13 13:45 ` Will Deacon
2021-12-13 14:01 ` Ard Biesheuvel
2021-12-13 16:42 ` Will Deacon [this message]
2021-12-15 14:13 ` Qian Cai
2021-12-15 16:02 ` Catalin Marinas
2021-12-15 16:04 ` David Hildenbrand
2021-12-16 3:00 ` Jianyong Wu
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=163941094777.2464379.2692109101400876104.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 \
/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).