From: syzbot ci <syzbot+cia9761817c4f42e6b@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: KEYS: Replace assoc_array with rhashtable
Date: Thu, 12 Nov 2026 20:58:33 -0800 [thread overview]
Message-ID: <6af698f9.e4c0560b.3d4154.0002.GAE@google.com> (raw)
syzbot ci has tested the following series
[v8] KEYS: Replace assoc_array with rhashtable
https://lore.kernel.org/all/20261110044043.2608600-1-jarkko@kernel.org
* [PATCH v8 1/3] KEYS: Introduce keyring_is_empty()
* [PATCH v8 2/3] KEYS: Replace assoc_array with rhashtable
* [PATCH v8 3/3] lib: Remove assoc_array
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/e8662095-cae7-4b37-9a5b-182619bd9a6a
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 7e1392a42ea288d70a266f6553fe06f57f8647ea
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/75f641d3-d64a-4016-a6db-a89bcebbee39/config
security/keys/keyring.c:1211:3: error: cannot jump from this goto statement to its label
security/keys/keyring.c:1205:3: error: cannot jump from this goto statement to its label
security/keys/keyring.c:1197:3: error: cannot jump from this goto statement to its label
***
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:
[agk@redhat.com akpm@linux-foundation.org alexs@kernel.org andrii@kernel.org ast@kernel.org bmarzins@redhat.com bpf@vger.kernel.org corbet@lwn.net daniel@iogearbox.net dhowells@redhat.com dm-devel@lists.linux.dev dzm91@hust.edu.cn ebiggers@kernel.org eddyz87@gmail.com emil@etsalapatis.com fsverity@lists.linux.dev ignat@linux.win ihor.solodrai@linux.dev jarkko@kernel.org jmorris@namei.org jolsa@kernel.org keyrings@vger.kernel.org linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org linux-security-module@vger.kernel.org martin.lau@linux.dev memxor@gmail.com mpatocka@redhat.com paul@paul-moore.com rdunlap@infradead.org serge@hallyn.com si.yanteng@linux.dev skhan@linuxfoundation.org snitzer@kernel.org song@kernel.org torvalds@linux-foundation.org tytso@mit.edu yonghong.song@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 other threads:[~2026-11-13 4:58 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=6af698f9.e4c0560b.3d4154.0002.GAE@google.com \
--to=syzbot+cia9761817c4f42e6b@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.