All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2d7d0fbb5fb979113ff3@syzkaller.appspotmail.com>
To: axboe@kernel.dk, eadavis@qq.com, gregkh@linuxfoundation.org,
	 hdanton@sina.com, linux-kernel@vger.kernel.org,
	ming.lei@redhat.com,  netdev@vger.kernel.org,
	nilay@linux.ibm.com, sunjunchao2870@gmail.com,
	 sunjunchao@bytedance.com, syzkaller-bugs@googlegroups.com,
	tj@kernel.org,  yukuai3@huawei.com
Subject: Re: [syzbot] [kernfs?] possible deadlock in kernfs_remove
Date: Tue, 28 Oct 2025 08:04:03 -0700	[thread overview]
Message-ID: <6900db63.050a0220.17b81f.0026.GAE@google.com> (raw)
In-Reply-To: <6890f71a.050a0220.7f033.0010.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 8f5845e0743bf3512b71b3cb8afe06c192d6acc4
Author: Julian Sun <sunjunchao2870@gmail.com>
Date:   Tue Aug 12 15:42:57 2025 +0000

    block: restore default wbt enablement

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13b977e2580000
start commit:   759dfc7d04ba netlink: avoid infinite retry looping in netl..
git tree:       net
kernel config:  https://syzkaller.appspot.com/x/.config?x=ac0888b9ad46cd69
dashboard link: https://syzkaller.appspot.com/bug?extid=2d7d0fbb5fb979113ff3
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1136d9bc580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1536d9bc580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: block: restore default wbt enablement

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-10-28 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 18:08 [syzbot] [kernfs?] possible deadlock in kernfs_remove syzbot
2025-08-05  2:27 ` Hillf Danton
2025-08-05  3:02   ` syzbot
2025-08-07 11:41 ` Edward Adam Davis
2025-08-07 14:02   ` syzbot
2025-08-07 14:15 ` Edward Adam Davis
2025-08-07 14:45   ` syzbot
2025-10-28 15:04 ` 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=6900db63.050a0220.17b81f.0026.GAE@google.com \
    --to=syzbot+2d7d0fbb5fb979113ff3@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=eadavis@qq.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nilay@linux.ibm.com \
    --cc=sunjunchao2870@gmail.com \
    --cc=sunjunchao@bytedance.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tj@kernel.org \
    --cc=yukuai3@huawei.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 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.