All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci0660e05383ed849c@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: sysctl: replace overloaded extra pointers with typed bounds and context
Date: Wed, 28 Oct 2026 22:44:12 -0700	[thread overview]
Message-ID: <6ae2dd2c.5451848c.f7707.0005.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] sysctl: replace overloaded extra pointers with typed bounds and context
https://lore.kernel.org/all/cover.1793204511.git.wen.yang@linux.dev
* [RFC PATCH 01/39] sysctl: replace overloaded extra pointers with typed bounds and context
* [RFC PATCH 02/39] test_sysctl: convert bounds to numeric values
* [RFC PATCH 03/39] sysctl: add KUnit coverage for numeric bounds and handlers
* [RFC PATCH 04/39] sysctl: cover runtime ranges and context lifecycles in KUnit
* [RFC PATCH 05/39] sysctl: cover priv in KUnit and the debug test module
* [RFC PATCH 06/39] sysctl: convert core table bounds to numeric values
* [RFC PATCH 07/39] sysctl: store architecture sysctl bounds by value
* [RFC PATCH 08/39] sysctl: store crypto sysctl bounds by value
* [RFC PATCH 09/39] sysctl: store device sysctl bounds by value
* [RFC PATCH 10/39] sysctl: store filesystem sysctl bounds by value
* [RFC PATCH 11/39] sysctl: store message-queue sysctl bounds by value
* [RFC PATCH 12/39] sysctl: store kernel sysctl bounds by value
* [RFC PATCH 13/39] sysctl: store memory-management sysctl bounds by value
* [RFC PATCH 14/39] sysctl: store IPv6 scalar sysctl bounds by value
* [RFC PATCH 15/39] sysctl: store netfilter scalar sysctl bounds by value
* [RFC PATCH 16/39] sysctl: store RPC sysctl bounds by value
* [RFC PATCH 17/39] sysctl: store remaining network sysctl bounds by value
* [RFC PATCH 18/39] sysctl: store security sysctl bounds by value
* [RFC PATCH 19/39] io_uring: store its sysctl bounds by value
* [RFC PATCH 20/39] sysctl: refresh dynamic scheduler and PID bounds per call
* [RFC PATCH 21/39] sysctl: refresh device-dependent bounds per call
* [RFC PATCH 22/39] sysctl: refresh namespace IPC bounds per call
* [RFC PATCH 23/39] yama: preserve scope locking with numeric sysctl bounds
* [RFC PATCH 24/39] net: refresh core sysctl limits without bound pointers
* [RFC PATCH 25/39] sctp: resolve numeric ranges from the current namespace
* [RFC PATCH 26/39] rds: preserve live reconnect limits with numeric bounds
* [RFC PATCH 27/39] ipv4: preserve live and vector bounds with numeric sysctls
* [RFC PATCH 28/39] net: refresh fragment and remaining dynamic sysctl bounds
* [RFC PATCH 29/39] neighbour: derive sysctl ownership independently of bounds
* [RFC PATCH 30/39] net: resolve sysctl owners from their backing data
* [RFC PATCH 31/39] ipvs: derive sysctl ownership from numeric storage
* [RFC PATCH 32/39] sysctl: remove obsolete nr_open bound variables
* [RFC PATCH 33/39] ipv6: move address sysctl context to priv
* [RFC PATCH 34/39] ipv4: move device sysctl context to priv
* [RFC PATCH 35/39] netfilter: move logger sysctl context to priv
* [RFC PATCH 36/39] parport: move device sysctl context to priv
* [RFC PATCH 37/39] net: move namespace sysctl context to priv
* [RFC PATCH 38/39] arm64: move vector-length sysctl context to priv
* [RFC PATCH 39/39] sysctl: remove the extra pointers and the compatibility bounds read

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/8e088b70-2ce9-4d52-8432-4d6d97db8a29

***

kernel build error

tree:      torvalds
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base:      c339f4010dea8b0d754f84ace70cd1b089878ef8
arch:      amd64
compiler:  Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/9097eda1-eee1-4198-9a33-035873aa2fda/config

net/unix/sysctl_net_unix.c:23:4: error: field designator 'extra1' does not refer to any field in type 'const struct ctl_table'
net/unix/sysctl_net_unix.c:24:4: error: field designator 'extra2' does not refer to any field in type 'const struct ctl_table'
net/unix/sysctl_net_unix.c:32:36: error: invalid application of 'sizeof' to an incomplete type 'const struct ctl_table[]'
net/unix/sysctl_net_unix.c:54:12: error: invalid application of 'sizeof' to an incomplete type 'const struct ctl_table[]'

***

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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[joel.granados@kernel.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org wen.yang@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-10-29  5:44 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=6ae2dd2c.5451848c.f7707.0005.GAE@google.com \
    --to=syzbot+ci0660e05383ed849c@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.