[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <433bb625-480f-46f2-986a-604fda49c046@stanley.mountain>
Date: Tue, 12 Nov 2024 17:00:22 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: "Serge E. Hallyn" <serge@...lyn.com>
Cc: Colin Ian King <colin.i.king@...il.com>,
Paul Moore <paul@...l-moore.com>, James Morris <jmorris@...ei.org>,
linux-security-module@...r.kernel.org,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] security: remove redundant assignment to variable
rc
On Tue, Nov 12, 2024 at 07:32:24AM -0600, Serge E. Hallyn wrote:
> On Tue, Nov 12, 2024 at 12:45:32PM +0000, Colin Ian King wrote:
> > In the case where rc is equal to EOPNOTSUPP it is being reassigned a
> > new value of zero that is never read. The following continue statement
> > loops back to the next iteration of the lsm_for_each_hook loop and
> > rc is being re-assigned a new value from the call to getselfattr.
> > The assignment is redundant and can be removed.
> >
> > Signed-off-by: Colin Ian King <colin.i.king@...il.com>
>
> Reviewed-by: Serge Hallyn <serge@...lyn.com>
>
> (long as it doesn't go to stable :)
>
There is a tag for fixes which would break stable.
Cc: <stable+noautosel@...nel.org> # reason goes here, and must be present
But this isn't a fix and it wouldn't break stable so probably that's not
appropriate.
regards,
dan carpenter
Powered by blists - more mailing lists