From: syzbot <syzbot+566d48f3784973a22771@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
ming.lei@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [scsi?] possible deadlock in sd_remove
Date: Thu, 02 Jan 2025 02:41:02 -0800 [thread overview]
Message-ID: <67766d3e.050a0220.3a8527.0038.GAE@google.com> (raw)
In-Reply-To: <20250102102816.1261-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
block/blk.h:728:7: error: use of undeclared identifier 'queue_dying'; did you mean 'cpu_dying'?
block/partitions/../blk.h:728:7: error: use of undeclared identifier 'queue_dying'; did you mean 'cpu_dying'?
block/partitions/../blk.h:734:7: error: use of undeclared identifier 'queue_dying'; did you mean 'cpu_dying'?
block/blk.h:734:7: error: use of undeclared identifier 'queue_dying'; did you mean 'cpu_dying'?
kernel/trace/../../block/blk.h:728:7: error: use of undeclared identifier 'queue_dying'; did you mean 'cpu_dying'?
kernel/trace/../../block/blk.h:734:7: error: use of undeclared identifier 'queue_dying'; did you mean 'cpu_dying'?
Tested on:
commit: cbacbf06 block: track queue dying state automatically ..
git tree: https://github.com/ming1/linux v6.13/block-fix
kernel config: https://syzkaller.appspot.com/x/.config?x=cd7202b56d469648
dashboard link: https://syzkaller.appspot.com/bug?extid=566d48f3784973a22771
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Note: no patches were applied.
next prev parent reply other threads:[~2025-01-02 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 2:29 [syzbot] [scsi?] possible deadlock in sd_remove syzbot
2024-12-31 8:00 ` syzbot
2025-01-02 10:28 ` Hillf Danton
2025-01-02 10:41 ` syzbot [this message]
2025-01-01 9:20 ` 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=67766d3e.050a0220.3a8527.0038.GAE@google.com \
--to=syzbot+566d48f3784973a22771@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ming.lei@redhat.com \
--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