From: Greg KH <gregkh@linuxfoundation.org>
To: He Lugang <helugang@uniontech.com>
Cc: stable@vger.kernel.org, Huacai Chen <chenhuacai@loongson.cn>
Subject: Re: [PATCH 6.6.y RESEND 2/2] LoongArch: Use accessors to page table entries instead of direct dereference
Date: Fri, 13 Sep 2024 16:27:54 +0200 [thread overview]
Message-ID: <2024091339-untangled-tracing-d859@gregkh> (raw)
In-Reply-To: <1197B2966A66F7F9+20240910131119.18625-2-helugang@uniontech.com>
On Tue, Sep 10, 2024 at 09:11:19PM +0800, He Lugang wrote:
> From: Huacai Chen <chenhuacai@loongson.cn>
>
> commit 4574815abf43e2bf05643e1b3f7a2e5d6df894f0 upstream
>
> As very well explained in commit 20a004e7b017cce282 ("arm64: mm: Use
> READ_ONCE/WRITE_ONCE when accessing page tables"), an architecture whose
> page table walker can modify the PTE in parallel must use READ_ONCE()/
> WRITE_ONCE() macro to avoid any compiler transformation.
>
> So apply that to LoongArch which is such an architecture, in order to
> avoid potential problems.
>
> Similar to commit edf955647269422e ("riscv: Use accessors to page table
> entries instead of direct dereference").
>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
You did not sign off on this, so I'm dropping it :(
prev parent reply other threads:[~2024-09-13 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 8:55 FAILED: patch "[PATCH] LoongArch: Use accessors to page table entries instead of" failed to apply to 6.6-stable tree gregkh
2024-09-10 13:01 ` [PATCH 6.6.y 1/2] LoongArch: KVM: Implement kvm mmu operations He Lugang
[not found] ` <20240910130104.17323-1-helugang@uniontech.com>
2024-09-10 13:01 ` [PATCH 6.6.y 2/2] LoongArch: Use accessors to page table entries instead of direct dereference He Lugang
2024-09-10 13:11 ` [PATCH 6.6.y RESEND 1/2] LoongArch: KVM: Implement kvm mmu operations He Lugang
[not found] ` <20240910131119.18625-1-helugang@uniontech.com>
2024-09-10 13:11 ` [PATCH 6.6.y RESEND 2/2] LoongArch: Use accessors to page table entries instead of direct dereference He Lugang
2024-09-13 14:27 ` Greg KH [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=2024091339-untangled-tracing-d859@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chenhuacai@loongson.cn \
--cc=helugang@uniontech.com \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox