From: syzbot <syzbot+1543a7d954d9c6d00407@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yss2813483011xxl@gmail.com
Subject: Re: [syzbot] [bridge?] KMSAN: uninit-value in netif_skb_features (4)
Date: Sat, 07 Mar 2026 23:45:02 -0800 [thread overview]
Message-ID: <69ad28fe.a70a0220.52840.0004.GAE@google.com> (raw)
In-Reply-To: <CAMa1Pe4_4UfoDdpxh-h5nWPz3FRk=8+BhLf1zkM=QggOR28hLQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1543a7d954d9c6d00407@syzkaller.appspotmail.com
Tested-by: syzbot+1543a7d954d9c6d00407@syzkaller.appspotmail.com
Tested on:
commit: c23719ab Merge tag 'x86-urgent-2026-03-08' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17af0806580000
kernel config: https://syzkaller.appspot.com/x/.config?x=242f02fcd3fbc8f3
dashboard link: https://syzkaller.appspot.com/bug?extid=1543a7d954d9c6d00407
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=101d3fe6580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-03-08 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMa1Pe4_4UfoDdpxh-h5nWPz3FRk=8+BhLf1zkM=QggOR28hLQ@mail.gmail.com>
2026-03-08 7:45 ` syzbot [this message]
[not found] <CAMa1Pe6wyZmz-3djTPESv8cxOuTciKxG5B74ctfZizhffLdSLA@mail.gmail.com>
2026-03-12 7:39 ` [syzbot] [bridge?] KMSAN: uninit-value in netif_skb_features (4) syzbot
[not found] <CAMa1Pe5kHL2Vi2GfvpwNxvy_-L1uySd9VZfqBFsN5KYxqg52nA@mail.gmail.com>
2026-03-11 18:04 ` syzbot
[not found] <CAMa1Pe4zkcBo-N=2esZxVDosKng88oa_eJeF5HkLykx1pgKjww@mail.gmail.com>
2026-03-07 13:35 ` syzbot
2025-10-07 6:40 [syzbot] [net?] " syzbot
2026-02-15 14:46 ` [syzbot] [bridge?] " 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=69ad28fe.a70a0220.52840.0004.GAE@google.com \
--to=syzbot+1543a7d954d9c6d00407@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yss2813483011xxl@gmail.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