All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4bb2305559463e8f6a2a@syzkaller.appspotmail.com>
To: axboe@kernel.dk, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org,  ming.lei@redhat.com,
	syzkaller-bugs@googlegroups.com,
	 thomas.hellstrom@linux.intel.com, tj@kernel.org
Subject: Re: [syzbot] [kernfs?] possible deadlock in kernfs_iop_getattr
Date: Sun, 20 Jul 2025 06:33:03 -0700	[thread overview]
Message-ID: <687cf00f.a70a0220.693ce.00c1.GAE@google.com> (raw)
In-Reply-To: <67eba499.050a0220.297a31.0009.GAE@google.com>

syzbot has bisected this issue to:

commit ffa1e7ada456087c2402b37cd6b2863ced29aff0
Author: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Date:   Tue Mar 18 09:55:48 2025 +0000

    block: Make request_queue lockdep splats show up earlier

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12d9a38c580000
start commit:   bf61759db409 Merge tag 'sched_ext-for-6.16-rc6-fixes' of g..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=11d9a38c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16d9a38c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=415e83411fefd73f
dashboard link: https://syzkaller.appspot.com/bug?extid=4bb2305559463e8f6a2a
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1242b7d4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12b6238c580000

Reported-by: syzbot+4bb2305559463e8f6a2a@syzkaller.appspotmail.com
Fixes: ffa1e7ada456 ("block: Make request_queue lockdep splats show up earlier")

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

      parent reply	other threads:[~2025-07-20 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  8:32 [syzbot] [kernfs?] possible deadlock in kernfs_iop_getattr syzbot
2025-04-10 20:33 ` syzbot
2025-07-20 23:30   ` Hillf Danton
2025-07-21  0:21     ` syzbot
2025-07-21  1:53   ` Hillf Danton
2025-07-21  2:17     ` syzbot
2025-07-20 13:33 ` 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=687cf00f.a70a0220.693ce.00c1.GAE@google.com \
    --to=syzbot+4bb2305559463e8f6a2a@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tj@kernel.org \
    /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.