From: "Theodore Ts'o" <tytso@mit.edu>
To: Baokun Li <libaokun1@huawei.com>
Cc: syzbot
<syzbot+list5ea887c46d22b2acf805@syzkaller.appspotmail.com>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, yangerkun <yangerkun@huawei.com>
Subject: Re: [syzbot] Monthly ext4 report (May 2023)
Date: Sat, 3 Jun 2023 00:30:28 -0400 [thread overview]
Message-ID: <20230603043028.GE1128875@mit.edu> (raw)
In-Reply-To: <d9be3fbf-023c-ac55-5097-ea3f43a946b4@huawei.com>
On Sat, Jun 03, 2023 at 10:05:44AM +0800, Baokun Li wrote:
>
> There are many sources of syzkaller issues, and the patches I send out
> to fix syzkaller issues add Reported-by to all but the ones that fix issues
> reported by our internal syzbot.
> However, there may be multiple syzbot reports for the same issue.
Yes, that happens a lot especially for Lockdep reports; depending on
how the reproducer triggers the locks in which order, there can often
be multiple different lockdep signatures, and Syzkaller can't tell
that they are all the same thing.
I tend to focus on syzbot reproducers on the upstream Linux instance,
rather than the Android-5.15 syzkaller instance. And that allows me
to use the ext4 subsystem dashboard available at:
https://syzkaller.appspot.com/upstream/s/ext4
It's against this list of reports that the Monthly ext4 report is
generated. So if people who are submitting fixes against syzkaller
reports, it would be nice if they were to check the ext4 dashboard
above to look for syzbot reports that might be also relevant to your
patch.
Thanks,
- Ted
next prev parent reply other threads:[~2023-06-03 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:38 [syzbot] Monthly ext4 report (May 2023) syzbot
2023-06-01 2:08 ` Baokun Li
2023-06-02 21:06 ` Theodore Ts'o
2023-06-03 2:05 ` Baokun Li
2023-06-03 4:30 ` Theodore Ts'o [this message]
2023-06-03 6:20 ` Baokun Li
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=20230603043028.GE1128875@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+list5ea887c46d22b2acf805@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yangerkun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.