From: Tong Tiangen <tongtiangen@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
James Morse <james.morse@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, <x86@kernel.org>,
"H . Peter Anvin" <hpa@zytor.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Xie XiuQi <xiexiuqi@huawei.com>
Subject: Re: [RFC PATCH -next V3 4/6] arm64: add copy_{to, from}_user to machine check safe
Date: Sat, 16 Apr 2022 15:41:09 +0800 [thread overview]
Message-ID: <6252f076-b74a-8dc8-9bc9-93aa70e844c5@huawei.com> (raw)
In-Reply-To: <306b1b09-487a-9ccd-4a63-8c78889492c6@arm.com>
在 2022/4/13 1:17, Robin Murphy 写道:
> On 12/04/2022 6:08 pm, Robin Murphy wrote:
> [...]
>>> @@ -62,7 +63,11 @@ SYM_FUNC_START(__arch_copy_from_user)
>>> ret
>>> // Exception fixups
>>> -9997: cmp dst, dstin
>>> +9997: mrs esr, esr_el1 // Check exception first
>>> + and esr, esr, #ESR_ELx_FSC
>>> + cmp esr, #ESR_ELx_FSC_EXTABT
>>
>> Should we be checking EC to make sure it's a data abort - and thus FSC
>> is valid - in the first place? I'm a little fuzzy on all the possible
>> paths into fixup_exception(), and it's not entirely obvious whether
>> this is actually safe or not.
>
> In fact, thinking some more about that, I don't think there should be
> any need for this sort of logic in these handlers at all. The
> fixup_exception() machinery should already know enough about the
> exception that's happened and the extable entry to figure this out and
> not bother calling the handler at all.
>
> Thanks,
> Robin.
> .
Hi Robin:
As you said, it seems that it's not good to judge esr here, how about
using the following method, i need your suggestion :)
+#define FIXUP_TYPE_NORMAL 0
+#define FIXUP_TYPE_MC 1
arch/arm64/mm/extable.c
static bool ex_handler_fixup(const struct exception_table_entry *ex,
- struct pt_regs *regs)
+ struct pt_regs *regs, int fixuptype)
{
+ regs->regs[16] = fixuptype;
[...]
}
bool fixup_exception(struct pt_regs *regs)
{
[...]
switch(ex->type) {
case EX_TYPE_UACCESS_MC:
- return ex_handler_fixup(ex, regs)
+ return ex_handler_fixup(ex, regs, FIXUP_TYPE_NORMAL)
break;
}
[...]
}
bool fixup_exception_mc(struct pt_regs *regs)
{
[...]
switch(ex->type) {
case EX_TYPE_UACCESS_MC:
- return ex_handler_fixup(ex, regs)
+ return ex_handler_fixup(ex, regs, FIXUP_TYPE_MC)
break;
}
[...]
}
arch/arm64/lib/copy_from_user.S
arch/arm64/lib/copy_to_user.S
+fixup_type .req x16
// Exception fixups
//x16: fixup type written by ex_handler_fixup
-9997: cmp dst, dstin
+9997: cmp fixup_type, #FIXUP_TYPE_MC
+ b.eq 9998f
+ cmp dst, dstin
b.ne 9998f
Thanks,
Tong.
next prev parent reply other threads:[~2022-04-16 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 7:25 [RFC PATCH -next V3 0/6]arm64: add machine check safe support Tong Tiangen
2022-04-12 7:25 ` [RFC PATCH -next V3 1/6] x86: fix function define in copy_mc_to_user Tong Tiangen
2022-04-12 11:49 ` Kefeng Wang
2022-04-13 6:01 ` Tong Tiangen
2022-04-12 7:25 ` [RFC PATCH -next V3 2/6] arm64: fix types in copy_highpage() Tong Tiangen
2022-04-12 11:50 ` Kefeng Wang
2022-04-12 7:25 ` [RFC PATCH -next V3 3/6] arm64: add support for machine check error safe Tong Tiangen
2022-04-12 13:08 ` Kefeng Wang
2022-04-13 14:41 ` Tong Tiangen
2022-04-12 7:25 ` [RFC PATCH -next V3 4/6] arm64: add copy_{to, from}_user to machine check safe Tong Tiangen
2022-04-12 17:08 ` Robin Murphy
2022-04-12 17:17 ` Robin Murphy
2022-04-16 7:41 ` Tong Tiangen [this message]
2022-04-13 6:36 ` Tong Tiangen
2022-04-13 7:30 ` Tong Tiangen
2022-04-12 7:25 ` [RFC PATCH -next V3 5/6] arm64: add {get, put}_user " Tong Tiangen
2022-04-12 7:25 ` [RFC PATCH -next V3 6/6] arm64: add cow " Tong Tiangen
2022-04-12 16:39 ` Robin Murphy
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=6252f076-b74a-8dc8-9bc9-93aa70e844c5@huawei.com \
--to=tongtiangen@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xiexiuqi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox