From: Joel Granados <joel.granados@kernel.org>
To: Alexey Gladkov <legion@kernel.org>
Cc: "Ondrej Mosnáček" <omosnacek@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Kees Cook" <kees@kernel.org>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Serge Hallyn" <serge@hallyn.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 2/6] sysctl: add unsigned int limit constants
Date: Thu, 24 Sep 2026 15:29:35 +0200 [thread overview]
Message-ID: <hc3jlqepedad5jbxz5rpskjktvbjcohorybc6kbtd7wtpajqi2@zftmndyhlw7a> (raw)
In-Reply-To: <92b31e85fbb91af953aee911a44787142cddee3f.1789987960.git.legion@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]
On Mon, Sep 21, 2026 at 12:54:49PM +0200, Alexey Gladkov wrote:
> Some sysctl handlers use unsigned int storage for their limit arguments.
> In particular, proc_dou8vec_minmax() expects extra1 and extra2 to point
> to unsigned int values even though the controlled data is an u8.
This one reads like a fix as opposed to part of your series. Is it
strictly needed for what you are proposing here?
>
> Provide shared unsigned int constants so typed sysctl descriptors can
> pass correctly typed min and max pointers without casting the existing
> int constants.
>
> Signed-off-by: Alexey Gladkov <legion@kernel.org>
> ---
> include/linux/sysctl.h | 7 +++++++
> kernel/sysctl.c | 3 +++
> 2 files changed, 10 insertions(+)
>
> diff --git a/include/linux/sysctl.h b/include/linux/sysctl.h
> index e5d7226ab6f5..7139a4c72736 100644
> --- a/include/linux/sysctl.h
> +++ b/include/linux/sysctl.h
> @@ -59,6 +59,12 @@ extern const int sysctl_vals[];
> #define SYSCTL_LONG_ONE ((void *)&sysctl_long_vals[1])
> #define SYSCTL_LONG_MAX ((void *)&sysctl_long_vals[2])
>
> +#define SYSCTL_UINT_ZERO ((unsigned int *)&sysctl_uint_vals[0])
> +#define SYSCTL_UINT_ONE ((unsigned int *)&sysctl_uint_vals[1])
> +#define SYSCTL_UINT_TWO ((unsigned int *)&sysctl_uint_vals[2])
> +#define SYSCTL_UINT_THREE ((unsigned int *)&sysctl_uint_vals[3])
> +#define SYSCTL_UINT_FOUR ((unsigned int *)&sysctl_uint_vals[4])
I would really like to avoid that. Its one of the things that should
probably go away in the future [1], [2], [3], [4]
[1] https://lore.kernel.org/all/875xyczpzm.fsf@email.froward.int.ebiederm.org/
[2] https://lore.kernel.org/all/tencent_C5E6023F97E7CC2A046AAEA09BC9ACF43907@qq.com/
[3] https://lore.kernel.org/all/cover.1739115369.git.wen.yang@linux.dev/
[4] https://lore.kernel.org/all/qnrzl4tjlgw5rzlvxavr3pt7fhkslnm4dd62q7uqzb3mfoa2jg@fuayx77rfcs6/
> +
> /*
> *
> * "dir" originates from read_iter (dir = 0) or write_iter (dir = 1)
> @@ -73,6 +79,7 @@ extern const int sysctl_vals[];
> #define SYSCTL_KERN_TO_USER(dir) (!dir)
>
> extern const unsigned long sysctl_long_vals[];
> +extern const unsigned int sysctl_uint_vals[];
>
> typedef int proc_handler(const struct ctl_table *ctl, int dir, void *buf,
> size_t *lenp, loff_t *ppos);
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index f7b75985d542..54edaa2fd5d5 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -29,6 +29,9 @@ EXPORT_SYMBOL(sysctl_vals);
> const unsigned long sysctl_long_vals[] = { 0, 1, LONG_MAX };
> EXPORT_SYMBOL_GPL(sysctl_long_vals);
>
> +const unsigned int sysctl_uint_vals[] = { 0, 1, 2, 3, 4 };
> +EXPORT_SYMBOL_GPL(sysctl_uint_vals);
> +
> #if defined(CONFIG_SYSCTL)
>
> /* Constants used for minimum and maximum */
> --
> 2.55.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2026-09-24 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 10:54 [PATCH v2 0/6] sysctl: add typed field descriptors Alexey Gladkov
2026-09-21 10:54 ` [PATCH v2 1/6] proc: sysctl: address table entries by index Alexey Gladkov
2026-09-21 10:54 ` [PATCH v2 2/6] sysctl: add unsigned int limit constants Alexey Gladkov
2026-09-24 13:29 ` Joel Granados [this message]
2026-09-24 15:08 ` Alexey Gladkov
2026-09-21 10:54 ` [PATCH v2 3/6] sysctl: add typed field descriptors Alexey Gladkov
2026-09-24 13:29 ` Joel Granados
2026-09-24 15:48 ` Alexey Gladkov
2026-09-21 10:54 ` [PATCH v2 4/6] sysctl: ipc: use typed fields for IPC namespace sysctls Alexey Gladkov
2026-09-21 10:54 ` [PATCH v2 5/6] sysctl: mq: " Alexey Gladkov
2026-09-21 10:54 ` [PATCH v2 6/6] sysctl: use typed fields for ucount limits Alexey Gladkov
2026-09-24 13:29 ` [PATCH v2 0/6] sysctl: add typed field descriptors Joel Granados
2026-09-24 14:46 ` Alexey Gladkov
2026-09-24 14:38 ` Joel Granados
2026-09-26 16:22 ` [PATCH v3 0/5] " Alexey Gladkov
2026-09-26 16:22 ` [PATCH v3 1/5] proc: sysctl: address table entries by index Alexey Gladkov
2026-09-26 16:22 ` [PATCH v3 2/5] sysctl: add typed field descriptors Alexey Gladkov
2026-09-26 16:22 ` [PATCH v3 3/5] sysctl: ipc: use typed fields for IPC namespace sysctls Alexey Gladkov
2026-09-26 16:22 ` [PATCH v3 4/5] sysctl: mq: " Alexey Gladkov
2026-09-26 16:22 ` [PATCH v3 5/5] sysctl: use typed fields for ucount limits Alexey Gladkov
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=hc3jlqepedad5jbxz5rpskjktvbjcohorybc6kbtd7wtpajqi2@zftmndyhlw7a \
--to=joel.granados@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kees@kernel.org \
--cc=legion@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnacek@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=serge@hallyn.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
all inboxes | Powered by JetHome®