From: Will Deacon <will@kernel.org>
To: Liu Shixin <liushixin2@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/mm: add pud_user_exec() check in pud_user_accessible_page()
Date: Thu, 5 Jan 2023 18:03:58 +0000 [thread overview]
Message-ID: <167293112314.1463291.1068267375917494044.b4-ty@kernel.org> (raw)
In-Reply-To: <20221122123137.429686-1-liushixin2@huawei.com>
On Tue, 22 Nov 2022 20:31:37 +0800, Liu Shixin wrote:
> Add check for the executable case in pud_user_accessible_page() too
> like what we did for pte and pmd.
>
>
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/mm: add pud_user_exec() check in pud_user_accessible_page()
https://git.kernel.org/arm64/c/730a11f982e6
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: Liu Shixin <liushixin2@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/mm: add pud_user_exec() check in pud_user_accessible_page()
Date: Thu, 5 Jan 2023 18:03:58 +0000 [thread overview]
Message-ID: <167293112314.1463291.1068267375917494044.b4-ty@kernel.org> (raw)
In-Reply-To: <20221122123137.429686-1-liushixin2@huawei.com>
On Tue, 22 Nov 2022 20:31:37 +0800, Liu Shixin wrote:
> Add check for the executable case in pud_user_accessible_page() too
> like what we did for pte and pmd.
>
>
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/mm: add pud_user_exec() check in pud_user_accessible_page()
https://git.kernel.org/arm64/c/730a11f982e6
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
next prev parent reply other threads:[~2023-01-05 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:31 [PATCH] arm64/mm: add pud_user_exec() check in pud_user_accessible_page() Liu Shixin
2022-11-22 12:31 ` Liu Shixin
2023-01-05 18:03 ` Will Deacon [this message]
2023-01-05 18:03 ` 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=167293112314.1463291.1068267375917494044.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=wangkefeng.wang@huawei.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 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.