[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200513005440.GK367616@optiplex-lnx>
Date: Tue, 12 May 2020 20:54:40 -0400
From: Rafael Aquini <aquini@...hat.com>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
keescook@...omium.org, akpm@...ux-foundation.org,
yzaikin@...gle.com, tytso@....edu
Subject: Re: [PATCH v2] kernel: sysctl: ignore out-of-range taint bits
introduced via kernel.tainted
On Wed, May 13, 2020 at 12:39:53AM +0000, Luis Chamberlain wrote:
> On Tue, May 12, 2020 at 06:39:46PM -0400, Rafael Aquini wrote:
> > Users with SYS_ADMIN capability can add arbitrary taint flags
> > to the running kernel by writing to /proc/sys/kernel/tainted
> > or issuing the command 'sysctl -w kernel.tainted=...'.
I just notice 2 minor 'screw ups' on my part in the commit log:
> > These interface, however, are open for any integer value
This one probably needs to be reprhased as:
"The interface, however, is ... "
> > and this might an invalid set of flags being committed to
and I'm missing a verb here, as it should read:
"and this might cause an invalid ... "
I hope these are easy fixes, in the pre-merge step. (Sorry!)
> > the tainted_mask bitset.
> >
> > This patch introduces a simple way for proc_taint() to ignore
> > any eventual invalid bit coming from the user input before
> > committing those bits to the kernel tainted_mask.
> >
> > Signed-off-by: Rafael Aquini <aquini@...hat.com>
>
> Reviewed-by: Luis Chamberlain <mcgrof@...nel.org>
>
Thanks!
-- Rafael
Powered by blists - more mailing lists