From: syzbot ci <syzbot+ci951a3f613d1ab765@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: devmem: support devmem with netkit devices
Date: Mon, 16 Mar 2026 21:48:08 -0700 [thread overview]
Message-ID: <69b8dd08.050a0220.12d28.016a.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] net: devmem: support devmem with netkit devices
https://lore.kernel.org/all/20260316-scratch-bobbyeshleman-tcp-dm-netkit5-v1-0-b53c8cd72b23@meta.com
* [PATCH net-next 1/6] net: devmem: support TX through netkit leased queues
* [PATCH net-next 2/6] selftests: drv-net: extract _find_bss_map_id helper in NetDrvContEnv
* [PATCH net-next 3/6] selftests: drv-net: add skip-config flag to ncdevmem
* [PATCH net-next 4/6] selftests: drv-net: add primary RX redirect support to NetDrvContEnv
* [PATCH net-next 5/6] selftests: drv-net: add netkit devmem RX test
* [PATCH net-next 6/6] selftests: drv-net: add netkit devmem TX test
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/e4c5419d-2378-4270-8913-bc133f1504a9
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 5446b8691eb8278f10deca92048fad84ffd1e4d5
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/fe1afa06-5895-437c-b959-86c0087a6d5b/config
net/core/netdev-genl.c:1095:58: error: no member named 'lease' in 'struct netdev_rx_queue'
***
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:
[almasrymina@google.com andrew@lunn.ch bobbyeshleman@gmail.com bobbyeshleman@meta.com bpf@vger.kernel.org davem@davemloft.net dw@davidwei.uk edumazet@google.com horms@kernel.org kuba@kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org netdev@vger.kernel.org pabeni@redhat.com sdf@fomichev.me shuah@kernel.org weibunny@fb.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-03-17 4:48 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=69b8dd08.050a0220.12d28.016a.GAE@google.com \
--to=syzbot+ci951a3f613d1ab765@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