On 2023/6/3 12:30, Theodore Ts'o wrote:
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
OK, later to fix any ext4 issue, I will check if the issue is in the ext4
subsystem dashboard.
Thanks!
--
With Best Regards,
Baokun Li
.
