From: Wen Yang <wen.yang@linux.dev>
To: Joel Granados <joel.granados@kernel.org>
Cc: David Laight <david.laight.linux@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 00/39] sysctl: replace overloaded extra pointers with typed bounds and context
Date: Fri, 13 Nov 2026 00:44:28 +0800 [thread overview]
Message-ID: <7ffdabc6-27f3-440b-97e6-94c7f66c807a@linux.dev> (raw)
In-Reply-To: <avRVHIx-6nA1mP2F@hobbes>
On 11/11/26 19:55, Joel Granados wrote:
> On Wed, Nov 11, 2026 at 01:45:15AM +0800, Wen Yang wrote:
>>
>>
>> On 11/9/26 18:07, Joel Granados wrote:
>>> On Sat, Nov 07, 2026 at 05:05:07PM +0000, David Laight wrote:
>>>> On Sat, 7 Nov 2026 16:27:39 +0100
>>>> Joel Granados <joel.granados@kernel.org> wrote:
>>>>
>>>>> On Mon, Nov 02, 2026 at 11:40:40PM +0800, Wen Yang wrote:
>>>>>>
>>>>>>
>>>>>> On 10/29/26 18:58, David Laight wrote:
>>>>>>> On Thu, 29 Oct 2026 00:34:39 +0800
>>>>>>> wen.yang@linux.dev wrote:
>>>>>>>> From: Wen Yang <wen.yang@linux.dev>
>>>>>>>>
>>>>>>>> struct ctl_table describes an entry with data, maxlen and, until this
>>>>>>>> series, two untyped misc pointers in extra1 and extra2. Those two pointers
>>>>>>>> have accumulated at least seven unrelated jobs: a fixed bound, a bound read
>>>>>>>> through a pointer on every call, an object or namespace pointer, a small
>>>>>>>> integer cookie encoded into the pointer, a lock signal, NULL standing for
>>>>>>>> "no bound", and a value the core itself casts to unsigned int while
>>>>>>>> validating a u8 range. Nothing in the entry says which job applies, so
>>>>>>>> readers infer it from the handler, and the core gets it wrong where it
>>>>>>>> treats extra1 as an unsigned int.
>>>>> <--- snip --->
> <--- snip --->
>> for (i = 0; i < head->ctl_table_size; i++) {
>> entry = sysctl_entry_at(head, i);
>> node = &head->node[i];
>> ...
>> }
>>
>> Insertion/deletion would take the node directly. Readdir would retain
>> its RB-tree node cursor, recovering each entry through that node's header:
>>
>> entry = sysctl_entry_at(node->header, node - node->header->node);
>>
>> No entry - head->ctl_table, caller slot constants or per-slot wrappers.
>> RB-tree order remains unchanged. Old APIs and generated directory/link
>> tables use sizeof(struct ctl_table).
>>
>> The two mechanisms have existing precedents:
>>
>> /* include/linux/bsearch.h: explicit element size */
>> pivot = base + (num >> 1) * size;
>> result = cmp(key, pivot);
>>
>> /* include/linux/hwmon-sysfs.h: extended descriptor */
>> struct sensor_device_attribute {
>> struct device_attribute dev_attr;
>> int index;
>> };
>>
>> /* drivers/hwmon/adcxx.c: ordinary device_attribute callback */
>> const struct sensor_device_attribute *attr = to_sensor_dev_attr(devattr);
>>
>> hwmon registers &ad_input[i].dev_attr via device_create_file(); the core
>> passes that same base descriptor to the callback. These are precedents
>> for explicit-size traversal and embedded callback context separately,
>> not an existing strided sysctl registration API.
>>
>> I agree that my fixed-slot solution adds maintenance overhead. Would
>> it make sense to explore this in three small steps?
>>
>> 1. Entry-access helpers, unchanged packed layout.
>> 2. Header stride and compatible registration wrappers.
>> 3. nf_log conversion and code/memory comparison.
>>
>> I would appreciate your thoughts on whether this is worth pursuing.
>
> Hey Wen
>
> Without a series, it is hard to see how everything fits. Maybe you can
> send out an RFC with just the changes to the sysctl core and one or two
> examples of how it would be used in the more involved users.
>
> The rest of the users can be "vibe coded" (so it compiles) and put into
> one big commit that we will ignore for the first RFC. Just so we get a
> clear idea of what you mean.
>
> Tell me what you think
>
Thanks.
That makes total sense. I will prepare a focused RFC series based on
the next-20261111 structured as follows:
Patch 1: sysctl: add numeric bounds and core stride infrastructure
(ctl_table_stride in header, sysctl_entry_at(), register_*_stride())
Patch 2: sysctl: cover numeric bounds and table containers in KUnit
Patch 3: netfilter: embed logger sysctl context using stride
(demonstrates the use of container_of(), and also eliminating some
wrapper functions)
Patch 4: net/ipv4: embed device sysctl context using stride
(demonstrates the use of container_of(), and also eliminating some
wrapper functions)
Patch 5: scripts/coccinelle: add script to detect and convert sysctl bounds
(provides automatic conversion and proves that no extra1/extra2 fields
remain)
The ctl_table_stride and type are packed as u16 in struct
ctl_table_header, yielding zero size increas.
I will send out this v2 RFC shortly for review.
--
Best wishes,
Wen
next prev parent reply other threads:[~2026-11-12 16:44 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 16:34 [RFC PATCH 00/39] sysctl: replace overloaded extra pointers with typed bounds and context wen.yang
2026-10-28 16:34 ` [RFC PATCH 01/39] " wen.yang
2026-10-28 21:09 ` David Laight
2026-11-07 17:43 ` Joel Granados
2026-10-28 16:34 ` [RFC PATCH 02/39] test_sysctl: convert bounds to numeric values wen.yang
2026-10-28 16:34 ` [RFC PATCH 03/39] sysctl: add KUnit coverage for numeric bounds and handlers wen.yang
2026-10-28 16:34 ` [RFC PATCH 04/39] sysctl: cover runtime ranges and context lifecycles in KUnit wen.yang
2026-10-28 16:34 ` [RFC PATCH 05/39] sysctl: cover priv in KUnit and the debug test module wen.yang
2026-10-28 16:34 ` [RFC PATCH 06/39] sysctl: convert core table bounds to numeric values wen.yang
2026-10-28 16:34 ` [RFC PATCH 07/39] sysctl: store architecture sysctl bounds by value wen.yang
2026-10-28 16:34 ` [RFC PATCH 08/39] sysctl: store crypto " wen.yang
2026-10-28 16:34 ` [RFC PATCH 09/39] sysctl: store device " wen.yang
2026-10-28 16:34 ` [RFC PATCH 10/39] sysctl: store filesystem " wen.yang
2026-10-28 16:34 ` [RFC PATCH 11/39] sysctl: store message-queue " wen.yang
2026-10-28 16:34 ` [RFC PATCH 12/39] sysctl: store kernel " wen.yang
2026-10-28 16:34 ` [RFC PATCH 13/39] sysctl: store memory-management " wen.yang
2026-10-28 16:34 ` [RFC PATCH 14/39] sysctl: store IPv6 scalar " wen.yang
2026-10-28 16:34 ` [RFC PATCH 15/39] sysctl: store netfilter " wen.yang
2026-10-28 16:34 ` [RFC PATCH 16/39] sysctl: store RPC " wen.yang
2026-10-28 16:34 ` [RFC PATCH 17/39] sysctl: store remaining network " wen.yang
2026-10-28 16:34 ` [RFC PATCH 18/39] sysctl: store security " wen.yang
2026-10-28 16:34 ` [RFC PATCH 19/39] io_uring: store its " wen.yang
2026-10-28 16:34 ` [RFC PATCH 20/39] sysctl: refresh dynamic scheduler and PID bounds per call wen.yang
2026-10-28 16:35 ` [RFC PATCH 21/39] sysctl: refresh device-dependent " wen.yang
2026-10-28 16:35 ` [RFC PATCH 22/39] sysctl: refresh namespace IPC " wen.yang
2026-10-28 16:35 ` [RFC PATCH 23/39] yama: preserve scope locking with numeric sysctl bounds wen.yang
2026-10-28 16:35 ` [RFC PATCH 24/39] net: refresh core sysctl limits without bound pointers wen.yang
2026-10-28 16:35 ` [RFC PATCH 25/39] sctp: resolve numeric ranges from the current namespace wen.yang
2026-10-28 16:35 ` [RFC PATCH 26/39] rds: preserve live reconnect limits with numeric bounds wen.yang
2026-10-28 16:35 ` [RFC PATCH 27/39] ipv4: preserve live and vector bounds with numeric sysctls wen.yang
2026-10-28 16:35 ` [RFC PATCH 28/39] net: refresh fragment and remaining dynamic sysctl bounds wen.yang
2026-10-28 16:35 ` [RFC PATCH 29/39] neighbour: derive sysctl ownership independently of bounds wen.yang
2026-10-28 16:35 ` [RFC PATCH 30/39] net: resolve sysctl owners from their backing data wen.yang
2026-10-28 16:35 ` [RFC PATCH 31/39] ipvs: derive sysctl ownership from numeric storage wen.yang
2026-10-28 16:35 ` [RFC PATCH 32/39] sysctl: remove obsolete nr_open bound variables wen.yang
2026-10-28 16:35 ` [RFC PATCH 33/39] ipv6: move address sysctl context to priv wen.yang
2026-10-28 16:35 ` [RFC PATCH 34/39] ipv4: move device " wen.yang
2026-10-28 16:35 ` [RFC PATCH 35/39] netfilter: move logger " wen.yang
2026-10-28 16:35 ` [RFC PATCH 36/39] parport: move device " wen.yang
2026-10-28 16:35 ` [RFC PATCH 37/39] net: move namespace " wen.yang
2026-10-28 16:35 ` [RFC PATCH 38/39] arm64: move vector-length " wen.yang
2026-10-28 16:35 ` [RFC PATCH 39/39] sysctl: remove the extra pointers and the compatibility bounds read wen.yang
2026-10-29 10:58 ` [RFC PATCH 00/39] sysctl: replace overloaded extra pointers with typed bounds and context David Laight
2026-11-02 15:40 ` Wen Yang
2026-11-02 16:54 ` David Laight
2026-11-04 18:32 ` Wen Yang
2026-11-07 15:27 ` Joel Granados
2026-11-07 17:05 ` David Laight
2026-11-09 10:07 ` Joel Granados
2026-11-10 17:45 ` Wen Yang
2026-11-11 11:55 ` Joel Granados
2026-11-12 16:44 ` Wen Yang [this message]
2026-11-09 9:25 ` Joel Granados
2026-11-07 21:26 ` Joel Granados
2026-11-12 10:22 ` Joel Granados
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=7ffdabc6-27f3-440b-97e6-94c7f66c807a@linux.dev \
--to=wen.yang@linux.dev \
--cc=david.laight.linux@gmail.com \
--cc=joel.granados@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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