From: Alexey Dobriyan <adobriyan@gmail.com>
To: christian@brauner.io
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v1 1/2] sysctl: cap to ULONG_MAX in proc_get_long()
Date: Mon, 15 Oct 2018 22:27:10 +0300 [thread overview]
Message-ID: <20181015192710.GA18693@avx2> (raw)
> int kstrtoul_bounded(const char *s, unsigned int base,
> char **trailing, unsigned long long *res)
NO! The whole point is not have million variants of slightly different
integer parsing functions.
Cap it in the sysctl -- noone would care.
next reply other threads:[~2018-10-15 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 19:27 Alexey Dobriyan [this message]
2018-10-15 19:32 ` Re: [PATCH v1 1/2] sysctl: cap to ULONG_MAX in proc_get_long() Christian Brauner
2018-10-15 21:15 ` 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=20181015192710.GA18693@avx2 \
--to=adobriyan@gmail.com \
--cc=christian@brauner.io \
--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 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.