From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: <elver@google.com>, <catalin.marinas@arm.com>, <will@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: kcsan: Fix kcsan test_barrier fail and panic
Date: Tue, 26 Apr 2022 23:39:44 +0800 [thread overview]
Message-ID: <fc736a39-2c21-70ac-4244-4c5b24ba7974@huawei.com> (raw)
In-Reply-To: <Ymfot/Le95Enuxqb@lakrids>
On 2022/4/26 20:42, Mark Rutland wrote:
> Hi,
>
> On Tue, Apr 26, 2022 at 08:17:00AM +0000, Kefeng Wang wrote:
>> As "kcsan: Support detecting a subset of missing memory barriers"
>> introduced KCSAN_STRICT which make kcsan detects more missing memory
>> barrier, but arm64 don't have KCSAN instrumentation for barriers, so
>> the new selftest test_barrier() will fail, then panic.
>>
>> Let's prefix all barriers with __ on arm64, as asm-generic/barriers.h
>> defined the final instrumented version of these barriers, which will
>> fix the above issues.
>>
>> Fixes: dd03762ab608 ("arm64: Enable KCSAN")
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> I don't think the Fixes tag is necessary given this is a new feature
> which depends upon EXPERT, and I'm worried it encourages backporting
> this into a kernel where it would be broken, so I'd prefer we drop that
> tag.
>
> IIUC when we originially looked at this the instrumentation wasn't safe
> and would violate noinstr requirements. Looking at linux/kcsan-checks.h,
> the comments block for __KCSAN_BARRIER_TO_SIGNAL_FENCE() say that it
> will respect __nokcsan, so it looks like that might be safe now.
>
> It looks like that's the case as of commit:
>
> bd3d5bd1a0ad3864 ("kcsan: Support WEAK_MEMORY with Clang where no objtool support exists")
>
> ... which requires clang 14.0.0+.
>
> That looks to have gone in concurrently with dd03762ab608, but is
> clearly a prerequisite, so as above I'd strongly prefer we drop the
> Fixes tag.
Sure, the "kcsan: Support detecting a subset of missing memory
barriers"[1] and
dd03762ab608 "arm64: Enable KCSAN" are both merged in v5.17. I will
drop the Fixes tag.
> It would be good if we could note that explicitly in the commit message.
I will add some message into v2.
>
> Have you eyeballed the generated assembly to verify that this works as
> expected for __no_kcsan ?
Look good, will recheck it.
>
> Thanks,
> Mark.
[1]
https://patchwork.kernel.org/project/linux-mm/cover/20211130114433.2580590-1-elver@google.com/
prev parent reply other threads:[~2022-04-26 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 8:17 Kefeng Wang
2022-04-26 12:10 ` Marco Elver
2022-04-26 12:50 ` Mark Rutland
2022-04-28 10:49 ` Will Deacon
2022-04-26 15:13 ` Kefeng Wang
2022-04-26 12:42 ` Mark Rutland
2022-04-26 15:39 ` Kefeng Wang [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=fc736a39-2c21-70ac-4244-4c5b24ba7974@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=elver@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®