The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+baee8591f336cab0958b@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?] general protection fault in bch2_snapshot_tree_oldest_subvol
Date: Fri, 11 Apr 2025 08:52:03 -0700	[thread overview]
Message-ID: <67f93aa3.050a0220.2c5fcf.0000.GAE@google.com> (raw)
In-Reply-To: <m2o6x2r9s1.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:         900241a5 Merge tag 'drm-fixes-2025-04-11-1' of https:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1314c870580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fb8650d88e9fb80f
dashboard link: https://syzkaller.appspot.com/bug?extid=baee8591f336cab0958b
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16f08870580000


  reply	other threads:[~2025-04-11 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03 20:50 [syzbot] [bcachefs?] general protection fault in bch2_snapshot_tree_oldest_subvol syzbot
2025-04-04 16:41 ` syzbot
2025-04-11 15:35 ` Charalampos Mitrodimas
2025-04-11 15:52   ` syzbot [this message]
2025-04-11 17:24   ` Kent Overstreet

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=67f93aa3.050a0220.2c5fcf.0000.GAE@google.com \
    --to=syzbot+baee8591f336cab0958b@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