From: syzbot ci <syzbot+ci3f3836f6436f8ff4@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: rhashtable: Restore insecure_elasticity toggle
Date: Fri, 17 Apr 2026 19:35:54 -0700 [thread overview]
Message-ID: <69e2ee0a.a00a0220.1bd0ca.0035.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] rhashtable: Restore insecure_elasticity toggle
https://lore.kernel.org/all/aeLgjAeJuidWNy3N@gondor.apana.org.au
* [PATCH] rhashtable: Restore insecure_elasticity toggle
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/43c0803b-4513-4474-86b2-94c9aade1dbf
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: eb0d6d97c27c29cd7392c8fd74f46edf7dff7ec2
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/ae1f60dc-d352-41b5-a103-69104326b619/config
./include/linux/rhashtable.h:824:32: error: member reference type 'struct rhashtable_params' is not a pointer; did you mean to use '.'?
.+./include/linux/rhashtable.h:832:13: error: member reference type 'struct rhashtable_params' is not a pointer; did you mean to use '.'?
./include/linux/rhashtable.h:832:13: error: member reference type 'struct rhashtable_params' is not a pointer; did you mean to use '.'?
lib/rhashtable.c:541:31: error: member reference type 'struct rhashtable_params' is not a pointer; did you mean to use '.'?
lib/rhashtable.c:572:12: error: member reference type 'struct rhashtable_params' is not a pointer; did you mean to use '.'?
***
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.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[arighi@nvidia.com changwoo@igalia.com emil@etsalapatis.com fw@strlen.de herbert@gondor.apana.org.au linux-crypto@vger.kernel.org linux-kernel@vger.kernel.org neil@brown.name netdev@vger.kernel.org sched-ext@lists.linux.dev tgraf@suug.ch tj@kernel.org void@manifault.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-04-18 2:35 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=69e2ee0a.a00a0220.1bd0ca.0035.GAE@google.com \
--to=syzbot+ci3f3836f6436f8ff4@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