From: syzbot ci <syzbot+ci3a48de5f63347675@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: tcp: rework tcp_v{4,6}_send_check()
Date: Tue, 03 Feb 2026 09:23:56 -0800 [thread overview]
Message-ID: <69822f2c.a00a0220.34fa92.0008.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] tcp: rework tcp_v{4,6}_send_check()
https://lore.kernel.org/all/20260203144053.83193-1-edumazet@google.com
* [PATCH net-next 1/3] tcp: inline __tcp_v4_send_check()
* [PATCH net-next 2/3] tcp: move tcp_v6_send_check() to tcp_output.c
* [PATCH net-next 3/3] tcp: make tcp_v{4,6}_send_check() static
and found the following issue:
SYZFATAL: image testing failed w/o kernel bug
Full report is available here:
https://ci.syzbot.org/series/69387f66-a7c3-46d7-a4a7-4c8bb1341763
***
SYZFATAL: image testing failed w/o kernel bug
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: fae1c659d7bd5640012be21b5b5d6490b83c0df8
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/3f3e530e-7dda-4f62-bcb7-114852e1f2c6/config
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[davem@davemloft.net edumazet@google.com eric.dumazet@gmail.com horms@kernel.org kuba@kernel.org kuniyu@google.com ncardwell@google.com netdev@vger.kernel.org pabeni@redhat.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-02-03 17:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69822f2c.a00a0220.34fa92.0008.GAE@google.com \
--to=syzbot+ci3a48de5f63347675@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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