From: Catalin Marinas <catalin.marinas@arm.com>
To: Yang Shi <yang@os.amperecomputing.com>
Cc: will@kernel.org, anshuman.khandual@arm.com,
scott@os.amperecomputing.com, cl@gentwo.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [v4 PATCH] arm64: mm: force write fault for atomic RMW instructions
Date: Fri, 14 Jun 2024 13:20:30 +0100 [thread overview]
Message-ID: <Zmw1jltdkMrTrT_l@arm.com> (raw)
In-Reply-To: <20240605203723.643329-1-yang@os.amperecomputing.com>
On Wed, Jun 05, 2024 at 01:37:23PM -0700, Yang Shi wrote:
> +static __always_inline bool aarch64_insn_is_class_cas(u32 insn)
> +{
> + return aarch64_insn_is_cas(insn) ||
> + aarch64_insn_is_casp(insn);
> +}
> +
> +/*
> + * Exclude unallocated atomic instructions and LD64B/LDAPR.
> + * The masks and values were generated by using Python sympy module.
> + */
> +static __always_inline bool aarch64_atomic_insn_has_wr_perm(u32 insn)
> +{
> + return ((insn & 0x3f207c00) == 0x38200000) ||
> + ((insn & 0x3f208c00) == 0x38200000) ||
> + ((insn & 0x7fe06c00) == 0x78202000) ||
> + ((insn & 0xbf204c00) == 0x38200000);
> +}
This is still pretty opaque if we want to modify it in the future. I
guess we could add more tests on top but it would be nice to have a way
to re-generate these masks. I'll think about, for now these tests would
do.
> @@ -511,6 +539,7 @@ static int __kprobes do_page_fault(unsigned long far, unsigned long esr,
> unsigned long addr = untagged_addr(far);
> struct vm_area_struct *vma;
> int si_code;
> + bool may_force_write = false;
>
> if (kprobe_page_fault(regs, esr))
> return 0;
> @@ -547,6 +576,7 @@ static int __kprobes do_page_fault(unsigned long far, unsigned long esr,
> /* If EPAN is absent then exec implies read */
> if (!alternative_has_cap_unlikely(ARM64_HAS_EPAN))
> vm_flags |= VM_EXEC;
> + may_force_write = true;
> }
>
> if (is_ttbr0_addr(addr) && is_el1_permission_fault(addr, esr, regs)) {
> @@ -568,6 +598,12 @@ static int __kprobes do_page_fault(unsigned long far, unsigned long esr,
> if (!vma)
> goto lock_mmap;
>
> + if (may_force_write && (vma->vm_flags & VM_WRITE) &&
> + is_el0_atomic_instr(regs)) {
> + vm_flags = VM_WRITE;
> + mm_flags |= FAULT_FLAG_WRITE;
> + }
I think we can get rid of may_force_write and just test (vm_flags &
VM_READ).
--
Catalin
next prev parent reply other threads:[~2024-06-14 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 20:37 [v4 PATCH] arm64: mm: force write fault for atomic RMW instructions Yang Shi
2024-06-05 20:37 ` Yang Shi
2024-06-06 8:49 ` David Hildenbrand
2024-06-06 8:49 ` David Hildenbrand
2024-06-14 12:20 ` Catalin Marinas [this message]
2024-06-26 18:45 ` Yang Shi
2024-06-26 20:50 ` Yang Shi
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=Zmw1jltdkMrTrT_l@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=cl@gentwo.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@os.amperecomputing.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.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.