[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJrkeJTCrajYh3oCnYsfLCtL+LBvRbMn75p4=gxKzBpcQ@mail.gmail.com>
Date: Mon, 30 Apr 2018 15:40:29 -0700
From: Kees Cook <keescook@...omium.org>
To: Waiman Long <longman@...hat.com>
Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>,
LKML <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
linux-doc@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>,
Matthew Wilcox <willy@...radead.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH v6 3/8] sysctl: Warn when a clamped sysctl parameter is
set out of range
I like this series overall, thanks! No objections from me. One thing I
noted, though:
On Fri, Apr 27, 2018 at 2:00 PM, Waiman Long <longman@...hat.com> wrote:
> if (param->min && *param->min > val) {
> if (clamp) {
> val = *param->min;
> + clamped = true;
> } else {
> return -EINVAL;
> }
This appears as a common bit of logic in many places in the series. It
seems like it'd make sense to make this a helper of some kind?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists