From: Niklas Cassel <cassel@kernel.org>
To: syzbot <syzbot+1f77b8ca15336fff21ff@syzkaller.appspotmail.com>,
syzkaller@googlegroups.com
Cc: dlemoal@kernel.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ide?] UBSAN: shift-out-of-bounds in ata_qc_issue
Date: Thu, 19 Feb 2026 23:44:32 +0100 [thread overview]
Message-ID: <aZeRycd4R-xG9Z3p@ryzen> (raw)
In-Reply-To: <6994d5c7.a70a0220.2c38d7.010b.GAE@google.com>
Hello syzkaller folks,
We syzkaller seems to have found a bug that it can reproduce very easily.
Looking at the dashboard for this bug:
https://syzkaller.appspot.com/bug?extid=1f77b8ca15336fff21ff
It has so far been reproduced 4 times in 3 days.
However, there is no reproducer yet.
Any advice on how we can try to trigger this without an exact reproducer
available yet?
Kind regards,
Niklas
On Tue, Feb 17, 2026 at 12:55:35PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: ca4ee40bf13d Partly revert "drm/hyperv: Remove reference t..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13c6c722580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a771bfd268751cd6
> dashboard link: https://syzkaller.appspot.com/bug?extid=1f77b8ca15336fff21ff
> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
>
> Unfortunately, I don't have any reproducer for this issue yet.
prev parent reply other threads:[~2026-02-19 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 20:55 [syzbot] [ide?] UBSAN: shift-out-of-bounds in ata_qc_issue syzbot
2026-02-18 9:45 ` Niklas Cassel
2026-02-19 1:33 ` Damien Le Moal
2026-02-20 0:55 ` Niklas Cassel
2026-02-20 1:06 ` Damien Le Moal
2026-02-20 9:17 ` Dmitry Vyukov
2026-02-20 9:27 ` Niklas Cassel
2026-02-19 22:44 ` Niklas Cassel [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=aZeRycd4R-xG9Z3p@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1f77b8ca15336fff21ff@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@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