From: syzbot <syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: WARNING in print_bfs_bug
Date: Tue, 05 Mar 2024 17:10:09 -0800 [thread overview]
Message-ID: <000000000000ba20260612f39ed4@google.com> (raw)
In-Reply-To: <000000000000e5ee7305f0f975e8@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: WARNING in print_bfs_bug
Author: david@fromorbit.com
Not obviously an XFS bug. This is an error coming from internal
lockdep code and many of the reproducers don't involve XFS at all.
e.g. some are are caused purely by netlink tests. But this isn't a
netlink bug, either, as the error message indicates lockdep failed
to traverse the dependency graph for some reason.
#syz set subsystems: kernel
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2024-03-06 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 15:51 [syzbot] WARNING in print_bfs_bug (2) syzbot
2023-04-29 13:38 ` [syzbot] [net?] " syzbot
2023-04-29 22:54 ` syzbot
2023-05-03 2:49 ` Tzung-Bi Shih
2023-05-05 13:27 ` Mark Brown
2024-03-06 1:10 ` syzbot [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:
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=000000000000ba20260612f39ed4@google.com \
--to=syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox