From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+5c5d41e80248d610221f@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] general protection fault in blk_mq_free_tags_callback
Date: Tue, 23 Sep 2025 15:21:38 +0800 [thread overview]
Message-ID: <20250923072139.7466-1-hdanton@sina.com> (raw)
In-Reply-To: <68d1b079.a70a0220.1b52b.0000.GAE@google.com>
> Date: Mon, 22 Sep 2025 13:24:25 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 846bd2225ec3 Add linux-next specific files for 20250919
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=13c238e2580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
> dashboard link: https://syzkaller.appspot.com/bug?extid=5c5d41e80248d610221f
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155e427c580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17bb8142580000
#syz test linux-next master
--- x/block/blk-mq-tag.c
+++ y/block/blk-mq-tag.c
@@ -565,6 +565,7 @@ struct blk_mq_tags *blk_mq_init_tags(uns
if (!tags)
return NULL;
+ INIT_LIST_HEAD(&tags->page_list);
tags->nr_tags = total_tags;
tags->nr_reserved_tags = reserved_tags;
spin_lock_init(&tags->lock);
--- x/arch/x86/kvm/emulate.c
+++ y/arch/x86/kvm/emulate.c
@@ -4001,7 +4001,6 @@ static int check_perm_out(struct x86_emu
#define D2bv(_f) D((_f) | ByteOp), D(_f)
#define D2bvIP(_f, _i, _p) DIP((_f) | ByteOp, _i, _p), DIP(_f, _i, _p)
#define I2bv(_f, _e) I((_f) | ByteOp, _e), I(_f, _e)
-#define F2bv(_f, _e) F((_f) | ByteOp, _e), F(_f, _e)
#define I2bvIP(_f, _e, _i, _p) \
IIP((_f) | ByteOp, _e, _i, _p), IIP(_f, _e, _i, _p)
@@ -4088,8 +4087,8 @@ static const struct opcode group4[] = {
};
static const struct opcode group5[] = {
- F(DstMem | SrcNone | Lock, em_inc),
- F(DstMem | SrcNone | Lock, em_dec),
+ I(DstMem | SrcNone | Lock, em_inc),
+ I(DstMem | SrcNone | Lock, em_dec),
I(SrcMem | NearBranch | IsBranch | ShadowStack, em_call_near_abs),
I(SrcMemFAddr | ImplicitOps | IsBranch | ShadowStack, em_call_far),
I(SrcMem | NearBranch | IsBranch, em_jmp_abs),
--
next prev parent reply other threads:[~2025-09-23 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 20:24 syzbot
2025-09-22 22:58 ` Hillf Danton
2025-09-22 23:55 ` syzbot
2025-09-23 3:28 ` Ming Lei
2025-09-23 1:48 ` Hillf Danton
2025-09-23 2:25 ` syzbot
2025-09-23 6:20 ` Jens Axboe
2025-09-23 6:35 ` Yu Kuai
2025-09-23 7:21 ` Hillf Danton [this message]
2025-09-23 8:51 ` 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=20250923072139.7466-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+5c5d41e80248d610221f@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®