[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202005150904.743BB3E52@keescook>
Date: Fri, 15 May 2020 09:05:23 -0700
From: Kees Cook <keescook@...omium.org>
To: Xiaoming Ni <nixiaoming@...wei.com>
Cc: mcgrof@...nel.org, yzaikin@...gle.com, adobriyan@...il.com,
mingo@...nel.org, peterz@...radead.org, akpm@...ux-foundation.org,
yamada.masahiro@...ionext.com, bauerman@...ux.ibm.com,
gregkh@...uxfoundation.org, skhan@...uxfoundation.org,
dvyukov@...gle.com, svens@...ckframe.org, joel@...lfernandes.org,
tglx@...utronix.de, Jisheng.Zhang@...aptics.com, pmladek@...e.com,
bigeasy@...utronix.de, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, wangle6@...wei.com
Subject: Re: [PATCH 2/4] proc/sysctl: add shared variables -1
On Fri, May 15, 2020 at 05:06:28PM +0800, Xiaoming Ni wrote:
> On 2020/5/15 16:06, Kees Cook wrote:
> > On Fri, May 15, 2020 at 12:33:42PM +0800, Xiaoming Ni wrote:
> > > Add the shared variable SYSCTL_NEG_ONE to replace the variable neg_one
> > > used in both sysctl_writes_strict and hung_task_warnings.
> > >
> > > Signed-off-by: Xiaoming Ni <nixiaoming@...wei.com>
> > > ---
> > > fs/proc/proc_sysctl.c | 2 +-
> > > include/linux/sysctl.h | 1 +
> > > kernel/hung_task_sysctl.c | 3 +--
> > > kernel/sysctl.c | 3 +--
> >
> > How about doing this refactoring in advance of the extraction patch?
> Before advance of the extraction patch, neg_one is only used in one file,
> does it seem to have no value for refactoring?
I guess it doesn't matter much, but I think it's easier to review in the
sense that neg_one is first extracted and then later everything else is
moved.
--
Kees Cook
Powered by blists - more mailing lists