From: syzbot <syzbot+d99f3a288cc7d8ef60fb@syzkaller.appspotmail.com>
To: dharanitharan725@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] [media?] general protection fault in su3000_i2c_transfer
Date: Sun, 07 Dec 2025 20:13:02 -0800 [thread overview]
Message-ID: <6936504e.a70a0220.38f243.007f.GAE@google.com> (raw)
In-Reply-To: <20251208023151.6677-2-dharanitharan725@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+d99f3a288cc7d8ef60fb@syzkaller.appspotmail.com
Tested-by: syzbot+d99f3a288cc7d8ef60fb@syzkaller.appspotmail.com
Tested on:
commit: c2f2b01b Merge tag 'i3c/for-6.19' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11f7d21a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=530ad8e7aaef67e
dashboard link: https://syzkaller.appspot.com/bug?extid=d99f3a288cc7d8ef60fb
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1040aeb4580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-12-08 4:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251208023151.6677-2-dharanitharan725@gmail.com>
2025-12-08 4:13 ` syzbot [this message]
[not found] <20251208022423.6624-2-dharanitharan725@gmail.com>
2025-12-08 3:27 ` [syzbot] [usb?] [media?] general protection fault in su3000_i2c_transfer syzbot
2025-12-08 3:12 [PATCH] media: dw2102: validate I2C messages in su3000_i2c_transfer() Dharanitharan R
2025-12-08 4:00 ` [syzbot] [usb?] [media?] general protection fault in su3000_i2c_transfer 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=6936504e.a70a0220.38f243.007f.GAE@google.com \
--to=syzbot+d99f3a288cc7d8ef60fb@syzkaller.appspotmail.com \
--cc=dharanitharan725@gmail.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.