From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
<akpm@linux-foundation.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <linux-mm@kvack.org>, <hch@infradead.org>, <arnd@arndb.de>,
<anshuman.khandual@arm.com>
Subject: Re: [PATCH v4 0/2] arm64: Fix kcsan test_barrier fail and panic
Date: Mon, 23 May 2022 19:19:03 +0800 [thread overview]
Message-ID: <36746fdd-4021-e491-f8cb-40e372439c67@huawei.com> (raw)
In-Reply-To: <20220523112641.170060-1-wangkefeng.wang@huawei.com>
Sorry for using wrong script with uncorrected maintainers, please ignore.
On 2022/5/23 19:26, Kefeng Wang wrote:
> Fix selftest and kcsan_test() module fail when KCSAN_STRICT
> and KCSAN_WEAK_MEMORY enabled on ARM64.
>
> v4:
> - Use 2 spaces after a sentence-ending '.', suggested by Marco
> - Collect Ack/Review
>
> v3:
> - update dma_mb()'s description and add the generic definition,
> also asm-generic change is moved into patch1, suggested by Marco.
> v2:
> - Add documents about dma_mb(), suggested by Mike and Will.
> - drop Fixes tag and update changlog, suggested by Mike.
>
>
> Kefeng Wang (2):
> asm-generic: Add memory barrier dma_mb()
> arm64: kcsan: Support detecting more missing memory barriers
>
> Documentation/memory-barriers.txt | 11 ++++++-----
> arch/arm64/include/asm/barrier.h | 12 ++++++------
> include/asm-generic/barrier.h | 8 ++++++++
> 3 files changed, 20 insertions(+), 11 deletions(-)
>
next prev parent reply other threads:[~2022-05-23 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 11:26 Kefeng Wang
2022-05-23 11:19 ` Kefeng Wang [this message]
2022-05-23 11:26 ` [PATCH v4 1/2] asm-generic: Add memory barrier dma_mb() Kefeng Wang
2022-05-23 11:26 ` [PATCH v4 2/2] arm64: kcsan: Support detecting more missing memory barriers Kefeng Wang
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=36746fdd-4021-e491-f8cb-40e372439c67@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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