From: syzbot <syzbot+aec9606169fbc3a12ca6@syzkaller.appspotmail.com>
To: charmitro@posteo.net, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] WARNING in bch2_dev_free
Date: Wed, 09 Apr 2025 10:02:03 -0700 [thread overview]
Message-ID: <67f6a80b.050a0220.25d1c8.0007.GAE@google.com> (raw)
In-Reply-To: <m25xjds4e2.fsf@posteo.net>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: a2458824 Merge tag 'linux_kselftest-kunit-6.15-rc2' of..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153ffb4c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fb8650d88e9fb80f
dashboard link: https://syzkaller.appspot.com/bug?extid=aec9606169fbc3a12ca6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17b7fb4c580000
next prev parent reply other threads:[~2025-04-09 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 11:53 [syzbot] [bcachefs?] WARNING in bch2_dev_free syzbot
2025-04-09 16:09 ` Charalampos Mitrodimas
2025-04-09 17:02 ` syzbot [this message]
2025-04-09 21:51 ` Kent Overstreet
2025-04-12 18:04 ` [syzbot] #syz test syzbot
2025-04-12 18:11 ` [syzbot] #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5fc31936081919a8572a3d644f3fbb258038f337 syzbot
2025-04-18 0:37 ` [syzbot] syzbot
[not found] <20250412180428.244928-1-gshahrouzi@gmail.com>
2025-04-12 18:44 ` [syzbot] [bcachefs?] WARNING in bch2_dev_free syzbot
[not found] <20250412181140.245367-1-gshahrouzi@gmail.com>
2025-04-12 18:50 ` syzbot
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=67f6a80b.050a0220.25d1c8.0007.GAE@google.com \
--to=syzbot+aec9606169fbc3a12ca6@syzkaller.appspotmail.com \
--cc=charmitro@posteo.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--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