On Mon, Oct 7, 2019 at 12:07 PM Eric Biggers <ebiggers@xxxxxxxxxx> wrote:
>
> Seems this indicates a corrupt filesystem rather than a kernel bug, so using
> WARN_ON is not appropriate. It should either use pr_warn_once(), or be silent.
I was going to silence it for the actual 5.4 release, but I wanted to
see if anybody actually triggers it.
I didn't really _expect_ it to be triggered, to be honest, so it's
interesting that it did. What is syzbot doing?
If this is syzbot doing filesystem image randomization, then it falls
under "ok, expected, ignore it, we'll silence it for 5.4"
But if it's syzbot doing something else, then it would be interesting
to hear what it's up to.
Linus
