All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b63d677d63bcac06cf90@syzkaller.appspotmail.com>
To: bentiss@kernel.org, jikos@kernel.org,
	linux-input@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org,  stern@rowland.harvard.edu,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in s32ton (2)
Date: Thu, 17 Jul 2025 08:49:03 -0700	[thread overview]
Message-ID: <68791b6f.a70a0220.693ce.004b.GAE@google.com> (raw)
In-Reply-To: <15723551-960b-4257-bfbd-073e136deaa2@rowland.harvard.edu>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+b63d677d63bcac06cf90@syzkaller.appspotmail.com
Tested-by: syzbot+b63d677d63bcac06cf90@syzkaller.appspotmail.com

Tested on:

commit:         c2ca42f1 HID: core: do not bypass hid_hw_raw_request
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git
console output: https://syzkaller.appspot.com/x/log.txt?x=148b258c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ec692dfd475747ff
dashboard link: https://syzkaller.appspot.com/bug?extid=b63d677d63bcac06cf90
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14dd1382580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2025-07-17 15:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 17:10 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in s32ton (2) syzbot
2025-07-14 18:38 ` Alan Stern
2025-07-14 18:50   ` syzbot
2025-07-14 19:48   ` Alan Stern
2025-07-14 20:28     ` syzbot
2025-07-15 19:29     ` Alan Stern
2025-07-15 19:50       ` syzbot
2025-07-16 14:29         ` Alan Stern
2025-07-16 14:50           ` syzbot
2025-07-16 15:58           ` Alan Stern
2025-07-17 11:48             ` Benjamin Tissoires
2025-07-17 15:10               ` Alan Stern
2025-07-17 15:49                 ` syzbot [this message]
2025-07-18  2:33                   ` [PATCH] HID: core: Reject report fields with a size or count of 0 Alan Stern
2025-07-19  8:36                     ` Benjamin Tissoires
2025-07-19  8:40                       ` Benjamin Tissoires
2025-07-19 14:48                       ` Alan Stern
2025-07-21 13:05                         ` Benjamin Tissoires
2025-07-21 13:56                           ` Alan Stern
2025-07-23  9:32                             ` Benjamin Tissoires
2025-07-23 14:34                               ` Alan Stern
2025-07-23 14:37                                 ` [PATCH] HID: core: Harden s32ton() against conversion to 0 bits Alan Stern
2025-07-21 14:37                   ` [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in s32ton (2) Alan Stern
2025-07-21 15:23                     ` syzbot
2025-07-18 16:08       ` (subset) " Benjamin Tissoires
2025-07-23  9:36         ` Benjamin Tissoires
2025-07-25 11:46       ` Benjamin Tissoires

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=68791b6f.a70a0220.693ce.004b.GAE@google.com \
    --to=syzbot+b63d677d63bcac06cf90@syzkaller.appspotmail.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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.