From: syzbot <syzbot+9a4fbb77c9d4aacd3388@syzkaller.appspotmail.com>
To: hariconscious@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [tipc?] KMSAN: uninit-value in tipc_rcv (2)
Date: Sat, 20 Sep 2025 12:43:03 -0700 [thread overview]
Message-ID: <68cf03c7.050a0220.13cd81.0020.GAE@google.com> (raw)
In-Reply-To: <20250920170037.9612-1-hariconscious@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
net/tipc/node.c:2121:3: error: void function 'tipc_rcv' should not return a value [-Wreturn-mismatch]
Tested on:
commit: 3b08f56f Merge tag 'x86-urgent-2025-09-20' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7ff65239b4835001
dashboard link: https://syzkaller.appspot.com/bug?extid=9a4fbb77c9d4aacd3388
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=101470e2580000
next parent reply other threads:[~2025-09-20 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250920170037.9612-1-hariconscious@gmail.com>
2025-09-20 19:43 ` syzbot [this message]
[not found] <CABBwEEgK85XKVdisWmzKVUQS0ZKnVa0TmRQHP+g1t+mfEWpu0A@mail.gmail.com>
2025-11-22 10:11 ` [syzbot] [tipc?] KMSAN: uninit-value in tipc_rcv (2) syzbot
[not found] <0f7bf1a1-7708-b253-fd8a-3bfbefe4e309@gmail.com>
2025-11-18 13:28 ` syzbot
[not found] <CABBwEEhHeCq3Ry-6JoG1ruTTbfeRUKcYxTobQd88O8wYvOQBUQ@mail.gmail.com>
2025-11-07 10:58 ` syzbot
[not found] <5715ad57-d676-ecde-1636-1634b49316d6@gmail.com>
2025-11-07 9:21 ` syzbot
[not found] <e8b78334-cb9f-900b-f05a-23a0d0ee902a@gmail.com>
2025-11-07 6:46 ` syzbot
[not found] <20250919152337.47803-1-hariconscious@gmail.com>
2025-09-19 17:10 ` syzbot
2025-07-23 14:45 syzbot
2025-08-03 9:39 ` 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=68cf03c7.050a0220.13cd81.0020.GAE@google.com \
--to=syzbot+9a4fbb77c9d4aacd3388@syzkaller.appspotmail.com \
--cc=hariconscious@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