From: syzbot <syzbot+fcc47ba2476570cbbeb0@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] WARNING in blk_mq_start_request
Date: Tue, 07 Nov 2023 16:52:05 -0800 [thread overview]
Message-ID: <0000000000000014460609997fa2@google.com> (raw)
In-Reply-To: <tencent_C325838DE11216DD9C5DAA192E4FCA0DD207@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+fcc47ba2476570cbbeb0@syzkaller.appspotmail.com
Tested on:
commit: 4652b8e4 Merge tag '6.7-rc-ksmbd-server-fixes' of git:..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1629a00f680000
kernel config: https://syzkaller.appspot.com/x/.config?x=5316ad879647e3c5
dashboard link: https://syzkaller.appspot.com/bug?extid=fcc47ba2476570cbbeb0
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=107e3ac0e80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-11-08 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_C325838DE11216DD9C5DAA192E4FCA0DD207@qq.com>
2023-11-08 0:52 ` syzbot [this message]
2023-11-08 1:35 ` [syzbot] [PATCH] Test for 4652b8e4f3ff syzbot
2023-11-08 6:25 ` syzbot
2023-11-08 21:18 ` [syzbot] [block?] WARNING in blk_mq_start_request syzbot
2023-11-09 1:27 ` Chengming Zhou
2023-11-09 18:13 ` Bart Van Assche
2023-11-13 15:05 ` [External] " Chengming Zhou
2023-11-13 23:57 ` Bart Van Assche
2023-11-14 15:05 ` Chengming Zhou
[not found] <tencent_E23E9622360A4AE4747176DF66203CBD3609@qq.com>
2023-11-08 6:46 ` syzbot
[not found] <tencent_D46F8895D0EB56EF92CC4078B66CE02DC50A@qq.com>
2023-11-08 2:09 ` syzbot
2023-11-07 7:29 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=0000000000000014460609997fa2@google.com \
--to=syzbot+fcc47ba2476570cbbeb0@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--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 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.