From: syzbot ci <syzbot+cic2af1ade41d8728d@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: rxrpc: Miscellaneous fixes
Date: Thu, 26 Mar 2026 08:23:27 -0700 [thread overview]
Message-ID: <69c54f6f.050a0220.330c49.0005.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] rxrpc: Miscellaneous fixes
https://lore.kernel.org/all/20260326131838.634095-1-dhowells@redhat.com
* [PATCH net v3 01/11] rxrpc: Fix key quota calculation for multitoken keys
* [PATCH net v3 02/11] rxrpc: Fix key parsing memleak
* [PATCH net v3 03/11] rxrpc: Fix anonymous key handling
* [PATCH net v3 04/11] list: Move on_list_rcu() to list.h and add on_list() also
* [PATCH net v3 05/11] rxrpc: Fix call removal to use RCU safe deletion
* [PATCH net v3 06/11] rxrpc: Fix RxGK token loading to check bounds
* [PATCH net v3 07/11] rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial
* [PATCH net v3 08/11] rxrpc: Fix rack timer warning to report unexpected mode
* [PATCH net v3 09/11] rxrpc: Fix keyring reference count leak in rxrpc_setsockopt()
* [PATCH net v3 10/11] rxrpc: Fix key reference count leak from call->key
* [PATCH net v3 11/11] rxrpc: Fix to request an ack if window is limited
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/d0886195-b303-4030-a0d4-bfb5b219c6a2
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: c4ea7d8907cf72b259bf70bd8c2e791e1c4ff70f
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/ae589f6b-a0f1-44d0-ab85-ab14cf208472/config
fs/jffs2/nodemgmt.c:572:19: error: conflicting types for 'on_list'
fs/jffs2/nodemgmt.c:660:28: error: too many arguments to function call, expected single argument 'entry', have 2 arguments
***
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:
[alok.a.tiwari@oracle.com anderson@allelesecurity.com apparmor@lists.ubuntu.com davem@davemloft.net dhowells@redhat.com edumazet@google.com hminas@synopsys.com horms@kernel.org jaltman@auristor.com john.johansen@canonical.com kuba@kernel.org linux-afs@lists.infradead.org linux-kernel@vger.kernel.org linux-usb@vger.kernel.org marc.c.dionne@gmail.com marc.dionne@auristor.com mathieu.desnoyers@efficios.com netdev@vger.kernel.org pabeni@redhat.com security@1seal.org stable@kernel.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-03-26 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 15:23 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-20 17:19 [moderation/CI] Re: rxrpc: Miscellaneous fixes syzbot ci
2026-03-23 18:08 syzbot ci
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=69c54f6f.050a0220.330c49.0005.GAE@google.com \
--to=syzbot+cic2af1ade41d8728d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.