Theodore Ts'o
unread,Jun 3, 2023, 12:30:35 AM6/3/23Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Baokun Li, syzbot, adilger...@dilger.ca, linux...@vger.kernel.org, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, yangerkun
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