From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Jisheng Zhang <jszhang@kernel.org>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: mm: pass original fault address to handle_mm_fault() in PER_VMA_LOCK block
Date: Fri, 2 Jun 2023 13:33:17 +0100 [thread overview]
Message-ID: <168570736489.522333.367811133664601205.b4-ty@kernel.org> (raw)
In-Reply-To: <20230524131305.2808-1-jszhang@kernel.org>
On Wed, 24 May 2023 21:13:05 +0800, Jisheng Zhang wrote:
> When reading the arm64's PER_VMA_LOCK support code, I found a bit
> difference between arm64 and other arch when calling handle_mm_fault()
> during VMA lock-based page fault handling: the fault address is masked
> before passing to handle_mm_fault(). This is also different from the
> usage in mmap_lock-based handling. I think we need to pass the
> original fault address to handle_mm_fault() as we did in
> commit 84c5e23edecd ("arm64: mm: Pass original fault address to
> handle_mm_fault()").
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: mm: pass original fault address to handle_mm_fault() in PER_VMA_LOCK block
https://git.kernel.org/arm64/c/0e2aba694866
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2023-06-02 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 13:13 Jisheng Zhang
2023-05-25 17:03 ` Catalin Marinas
2023-06-02 12:33 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-24 13:12 Jisheng Zhang
2023-05-24 13:26 ` Jisheng Zhang
2023-05-24 14:39 ` Suren Baghdasaryan
2023-05-25 7:00 ` Anshuman Khandual
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=168570736489.522333.367811133664601205.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jszhang@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=surenb@google.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
all inboxes | Powered by JetHome®