From: syzbot ci <syzbot+cif3c0eb132e9fb2a6@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Deprecate Legacy IP
Date: Wed, 01 Apr 2026 07:27:43 -0700 [thread overview]
Message-ID: <69cd2b5f.050a0220.25c253.0476.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] Deprecate Legacy IP
https://lore.kernel.org/all/20260401074509.1897527-1-dwmw2@infradead.org
* [PATCH 1/6] net: Simplify tautological CONFIG_INET/CONFIG_IPV6 guards
* [PATCH 2/6] net: Add CONFIG_LEGACY_IP option
* [PATCH 3/6] net: Guard Legacy IP entry points with CONFIG_LEGACY_IP
* [PATCH 4/6] net: Make IPv4-only Kconfig options depend on LEGACY_IP
* [PATCH 5/6] net: Change CONFIG_INET to CONFIG_LEGACY_IP for IPv4-only code
* [PATCH 6/6] net: Warn when processes listen on AF_INET sockets
and found the following issue:
SYZFATAL: image testing failed w/o kernel bug
Full report is available here:
https://ci.syzbot.org/series/b4aa6e49-79ea-440f-b64a-304320faf474
***
SYZFATAL: image testing failed w/o kernel bug
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 0eeb0094ba0321f0927806857b5f01c1577bc245
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/49e58d6b-bfbd-4e6f-a974-079ccb12b0ce/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.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[alazar@nvidia.com andrew@lunn.ch andrii@kernel.org ast@kernel.org bpf@vger.kernel.org bridge@lists.linux.dev coreteam@netfilter.org daniel@iogearbox.net davem@davemloft.net dsahern@kernel.org dwmw2@infradead.org dwmw@amazon.co.uk eddyz87@gmail.com edumazet@google.com fw@strlen.de gal@nvidia.com gnault@redhat.com haoluo@google.com horms@kernel.org idosch@nvidia.com johannes@sipsolutions.net john.fastabend@gmail.com jolsa@kernel.org jon.maddog.hall@gmail.com kees@kernel.org kpsingh@kernel.org kuba@kernel.org kuniyu@google.com leon@kernel.org linux-kernel@vger.kernel.org linux-rdma@vger.kernel.org linux-wireless@vger.kernel.org martin.lau@linux.dev mbloch@nvidia.com ncardwell@google.com netdev@vger.kernel.org netfilter-devel@vger.kernel.org oss-drivers@corigine.com pabeni@redhat.com pablo@netfilter.org paul@paul-moore.com phil@nwl.cc razor@blackwall.org saeedm@nvidia.com sdf@fomichev.me song@kernel.org tariqt@nvidia.com torvalds@linux-foundation.org willemb@google.com yonghong.song@linux.dev]
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-04-01 14:27 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=69cd2b5f.050a0220.25c253.0476.GAE@google.com \
--to=syzbot+cif3c0eb132e9fb2a6@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