From: "Theodore Ts'o" <tytso@mit.edu>
To: Mike Christie <michael.christie@oracle.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+c2de99a72baaa06d31f3@syzkaller.appspotmail.com>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, llvm@lists.linux.dev, nathan@kernel.org,
ndesaulniers@google.com, syzkaller-bugs@googlegroups.com,
trix@redhat.com, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
martin.lau@linux.dev, bpf <bpf@vger.kernel.org>,
KP Singh <kpsingh@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [syzbot] [ext4?] [mm?] KCSAN: data-race in strscpy / strscpy (3)
Date: Fri, 21 Apr 2023 14:20:13 -0400 [thread overview]
Message-ID: <20230421182013.GA19035@mit.edu> (raw)
In-Reply-To: <13d484d3-d573-cd82-fff0-a35e27b8451e@oracle.com>
On Fri, Apr 21, 2023 at 12:40:45PM -0500, Mike Christie wrote:
>
> I didn't see the beginning of this thread and I think the part of the
> sysbot report that lists the patches/trees being used got cut off so
> I'm not 100% sure what's in the kernel.
Syzbot reported this on commit 76f598ba7d8e which is upstream after v6.3-rc6.
Cheers,
- Ted
next prev parent reply other threads:[~2023-04-21 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:33 syzbot
2023-04-21 14:43 ` Dmitry Vyukov
2023-04-21 14:58 ` Matthew Wilcox
2023-04-21 17:40 ` Mike Christie
2023-04-21 18:20 ` Theodore Ts'o [this message]
2023-04-24 7:59 ` Christian Brauner
2023-04-24 8:25 ` Dmitry Vyukov
2023-04-21 15:15 ` Alexei Starovoitov
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=20230421182013.GA19035@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dvyukov@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=michael.christie@oracle.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=syzbot+c2de99a72baaa06d31f3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=willy@infradead.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