[moderation/CI] Re: Deprecate Legacy IP
0 views
Skip to first unread message
syzbot ci
Apr 1, 2026, 10:27:45 AM (3 days ago) Apr 1
to syzkaller-upst...@googlegroups.com, syz...@lists.linux.dev
syzbot ci has tested the following series
[v1] Deprecate Legacy IP
https://lore.kernel.org/all/20260401074509....@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: syz...@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@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:
[ala...@nvidia.com and...@lunn.ch and...@kernel.org a...@kernel.org b...@vger.kernel.org bri...@lists.linux.dev core...@netfilter.org dan...@iogearbox.net da...@davemloft.net dsa...@kernel.org dw...@infradead.org dw...@amazon.co.uk edd...@gmail.com edum...@google.com f...@strlen.de g...@nvidia.com gna...@redhat.com hao...@google.com ho...@kernel.org ido...@nvidia.com joha...@sipsolutions.net john.fa...@gmail.com jo...@kernel.org jon.mad...@gmail.com ke...@kernel.org kps...@kernel.org ku...@kernel.org kun...@google.com le...@kernel.org linux-...@vger.kernel.org linux...@vger.kernel.org linux-w...@vger.kernel.org marti...@linux.dev mbl...@nvidia.com ncar...@google.com net...@vger.kernel.org netfilt...@vger.kernel.org oss-d...@corigine.com pab...@redhat.com pa...@netfilter.org pa...@paul-moore.com ph...@nwl.cc ra...@blackwall.org sae...@nvidia.com s...@fomichev.me so...@kernel.org tar...@nvidia.com torv...@linux-foundation.org wil...@google.com yongho...@linux.dev]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
[v1] Deprecate Legacy IP
https://lore.kernel.org/all/20260401074509....@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: syz...@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@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:
[ala...@nvidia.com and...@lunn.ch and...@kernel.org a...@kernel.org b...@vger.kernel.org bri...@lists.linux.dev core...@netfilter.org dan...@iogearbox.net da...@davemloft.net dsa...@kernel.org dw...@infradead.org dw...@amazon.co.uk edd...@gmail.com edum...@google.com f...@strlen.de g...@nvidia.com gna...@redhat.com hao...@google.com ho...@kernel.org ido...@nvidia.com joha...@sipsolutions.net john.fa...@gmail.com jo...@kernel.org jon.mad...@gmail.com ke...@kernel.org kps...@kernel.org ku...@kernel.org kun...@google.com le...@kernel.org linux-...@vger.kernel.org linux...@vger.kernel.org linux-w...@vger.kernel.org marti...@linux.dev mbl...@nvidia.com ncar...@google.com net...@vger.kernel.org netfilt...@vger.kernel.org oss-d...@corigine.com pab...@redhat.com pa...@netfilter.org pa...@paul-moore.com ph...@nwl.cc ra...@blackwall.org sae...@nvidia.com s...@fomichev.me so...@kernel.org tar...@nvidia.com torv...@linux-foundation.org wil...@google.com yongho...@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 all
Reply to author
Forward
0 new messages