From: syzbot <syzbot+0a36c1fec090c67a9885@syzkaller.appspotmail.com>
To: abhinav.ogl@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [i2c?] KMSAN: uninit-value in __i2c_smbus_xfer
Date: Thu, 29 May 2025 04:48:02 -0700 [thread overview]
Message-ID: <68384972.a70a0220.1765ec.0187.GAE@google.com> (raw)
In-Reply-To: <CAGR7w80dQ5hTj8ye0DLi7SwT9v53S+anDDpGjQw5suwEdGXVHw@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0a36c1fec090c67a9885@syzkaller.appspotmail.com
Tested-by: syzbot+0a36c1fec090c67a9885@syzkaller.appspotmail.com
Tested on:
commit: 90b83efa Merge tag 'bpf-next-6.16' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=178d2482580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1da44e3e5e6013db
dashboard link: https://syzkaller.appspot.com/bug?extid=0a36c1fec090c67a9885
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch: https://syzkaller.appspot.com/x/patch.diff?x=10c8ced4580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-05-29 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGR7w80dQ5hTj8ye0DLi7SwT9v53S+anDDpGjQw5suwEdGXVHw@mail.gmail.com>
2025-05-29 11:48 ` syzbot [this message]
[not found] <CAGR7w82vvJPoF4ptK5PvVCDSmK_PJ44DJyDBq0=q3_w-nKFc1A@mail.gmail.com>
2025-06-04 14:13 ` [syzbot] [i2c?] KMSAN: uninit-value in __i2c_smbus_xfer syzbot
[not found] <CAGR7w81Zq-HhXvfgXpRM9FPpy67uxQaM_DM8nwN5vEU23oPRqA@mail.gmail.com>
2025-05-29 9:12 ` syzbot
[not found] <CAGR7w83NuUmNhvLTHXC1g7O-dxJQw-Ur6Lsk+YgGtLafkOrdFQ@mail.gmail.com>
2025-05-28 16:57 ` syzbot
[not found] <CAGR7w82zibJcdbxq8d-VZDj-uO3kXZbMuSx=HZTMRVdfnLiaQA@mail.gmail.com>
2025-05-28 13:12 ` syzbot
2025-05-05 7:16 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=68384972.a70a0220.1765ec.0187.GAE@google.com \
--to=syzbot+0a36c1fec090c67a9885@syzkaller.appspotmail.com \
--cc=abhinav.ogl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).