From: Kees Cook <keescook@chromium.org>
To: Matteo Croce <mcroce@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH 1/2] proc/sysctl: add shared variables for range check
Date: Wed, 10 Apr 2019 15:18:33 -0700 [thread overview]
Message-ID: <CAGXu5jJJDzty8trTPmuxu0_K9xvf+nJ9HGuUE9NF-WOgesu9sQ@mail.gmail.com> (raw)
In-Reply-To: <20190408220925.13077-2-mcroce@redhat.com>
On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce <mcroce@redhat.com> wrote:
>
> In the sysctl code the proc_dointvec_minmax() function is often used to
> validate the user supplied value between an allowed range. This function
> uses the extra1 and extra2 members from struct ctl_table as minimum and
> maximum allowed value.
>
> On sysctl handler declaration, in every source file there are some readonly
> variables containing just an integer which address is assigned to the
> extra1 and extra2 members, so the sysctl range is enforced.
>
> The special values 0, 1 and INT_MAX are very often used as range boundary,
> leading duplication of variables like zero=0, one=1, int_max=INT_MAX in
> different source files:
>
> $ git grep -E '\.extra[12].*&(zero|one|int_max)' |wc -l
> 261
>
> This patch adds three variables for the most commonly used values, so they
> can be referenced instead of creating a local one for every object file.
>
> Signed-off-by: Matteo Croce <mcroce@redhat.com>
Oh, and for this patch: Yes please; let's get everyone to use these
instead of littering the kernel with (non-const!) copies of the same
thing. :)
Acked-by: Kees Cook <keescook@chromium.org>
-Kees
> ---
> fs/proc/proc_sysctl.c | 5 +++++
> include/linux/sysctl.h | 4 ++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/fs/proc/proc_sysctl.c b/fs/proc/proc_sysctl.c
> index d65390727541..e7a96169fced 100644
> --- a/fs/proc/proc_sysctl.c
> +++ b/fs/proc/proc_sysctl.c
> @@ -21,6 +21,11 @@ static const struct inode_operations proc_sys_inode_operations;
> static const struct file_operations proc_sys_dir_file_operations;
> static const struct inode_operations proc_sys_dir_operations;
>
> +/* shared constants to be used in various sysctls */
> +const int sysctl_zero = 0;
> +const int sysctl_one = 1;
> +const int sysctl_int_max = INT_MAX;
> +
> /* Support for permanently empty directories */
>
> struct ctl_table sysctl_mount_point[] = {
> diff --git a/include/linux/sysctl.h b/include/linux/sysctl.h
> index b769ecfcc3bd..f3b191799747 100644
> --- a/include/linux/sysctl.h
> +++ b/include/linux/sysctl.h
> @@ -37,6 +37,10 @@ struct ctl_table_root;
> struct ctl_table_header;
> struct ctl_dir;
>
> +extern const int sysctl_zero;
> +extern const int sysctl_one;
> +extern const int sysctl_int_max;
> +
> typedef int proc_handler (struct ctl_table *ctl, int write,
> void __user *buffer, size_t *lenp, loff_t *ppos);
>
> --
> 2.21.0
>
--
Kees Cook
next prev parent reply other threads:[~2019-04-10 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 22:09 [PATCH 0/2] sysctl: share commonly used constants Matteo Croce
2019-04-08 22:09 ` [PATCH 1/2] proc/sysctl: add shared variables for range check Matteo Croce
2019-04-10 22:18 ` Kees Cook [this message]
2019-04-08 22:09 ` [PATCH 2/2] kernel: use sysctl " Matteo Croce
2019-04-10 18:46 ` Kees Cook
2019-04-10 19:23 ` Matteo Croce
2019-04-10 21:50 ` Kees Cook
2019-04-10 22:30 ` Matteo Croce
2019-04-10 22:34 ` Kees Cook
2019-04-10 22:54 ` Matteo Croce
2019-04-10 22:59 ` Kees Cook
2019-04-16 23:45 ` Andrew Morton
2019-04-17 3:21 ` Kees Cook
2019-04-17 3:22 ` Kees Cook
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=CAGXu5jJJDzty8trTPmuxu0_K9xvf+nJ9HGuUE9NF-WOgesu9sQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=adobriyan@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mcroce@redhat.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;
as well as URLs for NNTP newsgroup(s).