All of
 help / color / mirror / Atom feed
From: Baokun Li <>
To: Theodore Ts'o <>
Cc: syzbot
	<>, <>,
	<>, <>,
	yangerkun <>,
	Baokun Li <>
Subject: Re: [syzbot] Monthly ext4 report (May 2023)
Date: Sat, 3 Jun 2023 14:20:34 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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:
> 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.

With Best Regards,
Baokun Li

      reply	other threads:[~2023-06-03  6:20 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
2023-06-03  6:20         ` Baokun Li [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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.