From: syzbot ci <syzbot+cieb7e65077a0bd1bf@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: page_pool: check if nmdesc->pp is !NULL to confirm its usage as pp for net_iov
Date: Thu, 16 Oct 2025 00:25:09 -0700 [thread overview]
Message-ID: <68f09dd5.050a0220.91a22.03ba.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] page_pool: check if nmdesc->pp is !NULL to confirm its usage as pp for net_iov
https://lore.kernel.org/all/20251016063657.81064-1-byungchul@sk.com
* [PATCH net-next] page_pool: check if nmdesc->pp is !NULL to confirm its usage as pp for net_iov
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/ad6ce078-6497-42e2-a2ef-5749153b9dc6
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 18a7e218cfcdca6666e1f7356533e4c988780b57
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/d3d59dee-0e1f-48be-8dc1-5e0f7bed50c3/config
net/core/netmem_priv.h:29:12: error: call to undeclared function 'netmem_to_nmdesc'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
net/core/netmem_priv.h:29:38: error: member reference type 'int' is not a pointer
***
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 ap420073@gmail.com asml.silence@gmail.com axboe@kernel.dk byungchul@sk.com davem@davemloft.net dtatulea@nvidia.com dw@davidwei.uk edumazet@google.com hawk@kernel.org horms@kernel.org ilias.apalodimas@linaro.org io-uring@vger.kernel.org kernel_team@skhynix.com kuba@kernel.org linux-kernel@vger.kernel.org max.byungchul.park@gmail.com netdev@vger.kernel.org pabeni@redhat.com sdf@fomichev.me toke@redhat.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-10-16 7:25 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=68f09dd5.050a0220.91a22.03ba.GAE@google.com \
--to=syzbot+cieb7e65077a0bd1bf@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