From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jann Horn" <jannh@google.com>, "Marco Elver" <elver@google.com>
Cc: "Dmitry Vyukov" <dvyukov@google.com>,
kasan-dev@googlegroups.com,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rwonce: handle KCSAN like KASAN in read_word_at_a_time()
Date: Tue, 25 Mar 2025 17:59:14 +0100 [thread overview]
Message-ID: <fbd8d426-e45f-4f2e-b201-20b8396b20f9@app.fastmail.com> (raw)
In-Reply-To: <CAG48ez2eECk+iU759BhPLrDJrGcBPT2dkAZg_O_c1fdD+HsifQ@mail.gmail.com>
On Tue, Mar 25, 2025, at 17:36, Jann Horn wrote:
> On Tue, Mar 25, 2025 at 5:31 PM Marco Elver <elver@google.com> wrote:
>> On Tue, 25 Mar 2025 at 17:06, Arnd Bergmann <arnd@arndb.de> wrote:
>> > On Tue, Mar 25, 2025, at 17:01, Jann Horn wrote:
>> > > Fixes: dfd402a4c4ba ("kcsan: Add Kernel Concurrency Sanitizer infrastructure")
>> > > Signed-off-by: Jann Horn <jannh@google.com>
> [...]
>> I have nothing pending yet. Unless you're very certain there'll be
>> more KCSAN patches,
>
> No, I don't know yet whether I'll have more KCSAN patches for 6.15.
>
>> I'd suggest that Arnd can take it. I'm fine with
>> KCSAN-related patches that aren't strongly dependent on each other
>> outside kernel/kcsan to go through whichever tree is closest.
>
> Sounds good to me.
Applied, should be able send the PR tomorrow with the rest of
my asm-generic changes.
Arnd
next prev parent reply other threads:[~2025-03-25 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 16:01 [PATCH] rwonce: handle KCSAN like KASAN in read_word_at_a_time() Jann Horn
2025-03-25 16:05 ` Arnd Bergmann
2025-03-25 16:31 ` Marco Elver
2025-03-25 16:36 ` Jann Horn
2025-03-25 16:59 ` Arnd Bergmann [this message]
2025-03-26 20:39 ` Nathan Chancellor
2025-03-26 20:44 ` Jann Horn
2025-03-26 21:21 ` Jann Horn
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=fbd8d426-e45f-4f2e-b201-20b8396b20f9@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.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