All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cif840d2fcd060ac40@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: rxrpc: Miscellaneous fixes
Date: Mon, 23 Mar 2026 11:08:33 -0700	[thread overview]
Message-ID: <69c181a1.050a0220.3bf4de.00a5.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] rxrpc: Miscellaneous fixes
https://lore.kernel.org/all/20260323150505.3513839-1-dhowells@redhat.com
* [PATCH net v2 01/10] rxrpc: Fix key quota calculation for multitoken keys
* [PATCH net v2 02/10] rxrpc: Fix key parsing memleak
* [PATCH net v2 03/10] rxrpc: Fix anonymous key handling
* [PATCH net v2 04/10] list: Move on_list_rcu() to list.h and add on_list() also
* [PATCH net v2 05/10] rxrpc: Fix call removal to use RCU safe deletion
* [PATCH net v2 06/10] rxrpc: Fix RxGK token loading to check bounds
* [PATCH net v2 07/10] rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial
* [PATCH net v2 08/10] rxrpc: Fix rack timer warning to report unexpected mode
* [PATCH net v2 09/10] rxrpc: Fix keyring reference count leak in rxrpc_setsockopt()
* [PATCH net v2 10/10] rxrpc: Fix key reference count leak from call->key

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/ef91e45d-b5ac-4a0a-b180-1f857d7ece93

***

kernel build error

tree:      net
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base:      bc0151c59e639c1311ee573434af74b4e2c81de4
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/b2c276be-a7c1-44a8-9c23-40e21255de69/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 horms@kernel.org jaltman@auristor.com john.johansen@canonical.com kuba@kernel.org linux-afs@lists.infradead.org linux-kernel@vger.kernel.org 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


             reply	other threads:[~2026-03-23 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 18:08 syzbot ci [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-26 15:23 [moderation/CI] Re: rxrpc: Miscellaneous fixes syzbot ci
2026-04-20 17:19 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=69c181a1.050a0220.3bf4de.00a5.GAE@google.com \
    --to=syzbot+cif840d2fcd060ac40@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.