From: syzbot <syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com>
To: deepak.takumi.120@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [nfc?] KMSAN: uninit-value in nci_dev_up (2)
Date: Wed, 17 Sep 2025 06:55:02 -0700 [thread overview]
Message-ID: <68cabdb6.050a0220.3c6139.0fa6.GAE@google.com> (raw)
In-Reply-To: <CAC_ur0pPzCg9kY==OJVRJG1jPuP67Upp2hBDMTWDxJaScekZwQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com
Tested-by: syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com
Tested on:
commit: 5aca7966 Merge tag 'perf-tools-fixes-for-v6.17-2025-09..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14cd8c7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1b093ccee5a9e08c
dashboard link: https://syzkaller.appspot.com/bug?extid=740e04c2a93467a0f8c8
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=13dfaf62580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-09-17 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC_ur0pPzCg9kY==OJVRJG1jPuP67Upp2hBDMTWDxJaScekZwQ@mail.gmail.com>
2025-09-17 13:55 ` syzbot [this message]
[not found] <CAC_ur0pGOubmRFViT7oV8_pE5FykkCESLftpN6dxAPF3fmUL5g@mail.gmail.com>
2025-09-25 12:15 ` [syzbot] [net?] [nfc?] KMSAN: uninit-value in nci_dev_up (2) syzbot
[not found] <CAC_ur0os0P5cA_=3LSkoffOtrTN84m9CNWtCH2NZXz642Oc2Bg@mail.gmail.com>
2025-09-18 17:59 ` syzbot
[not found] <CAC_ur0qzBK7KZCrme4RyZj=efQ1uaBgLNvs=28Dinj8VDBkbFA@mail.gmail.com>
2025-09-17 11:15 ` syzbot
2025-08-07 17:05 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=68cabdb6.050a0220.3c6139.0fa6.GAE@google.com \
--to=syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com \
--cc=deepak.takumi.120@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