[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190211212523.GU11489@garbanzo.do-not-panic.com>
Date: Mon, 11 Feb 2019 13:25:23 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: Christian Brauner <christian@...uner.io>
Cc: Alexey Dobriyan <adobriyan@...il.com>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
longman@...hat.com, linux@...inikbrodowski.net,
keescook@...omium.org, joe.lawrence@...hat.com,
ebiederm@...ssion.com, linux-api@...r.kernel.org
Subject: Re: + sysctl-return-einval-if-val-violates-minmax.patch added to -mm
tree
On Mon, Feb 11, 2019 at 10:19:19PM +0100, Christian Brauner wrote:
> On Tue, Feb 12, 2019 at 12:17:16AM +0300, Alexey Dobriyan wrote:
> > On Mon, Feb 11, 2019 at 01:06:32PM -0800, akpm@...ux-foundation.org wrote:
> >
> > > @@ -2848,8 +2848,10 @@ static int __do_proc_doulongvec_minmax(v
> >
> > > - if ((min && val < *min) || (max && val > *max))
> > > - continue;
> > > + if ((min && val < *min) || (max && val > *max)) {
> > > + err = -EINVAL;
> >
> > I was asked to return ERANGE in kstrto*().
>
> I think we discussed ERANGE vs EINVAL and decided EINVAL because there
> was precedence for other sysctls already.
Can you do a proper audit and see?
linux-api folks may care.
Luis
Powered by blists - more mailing lists