[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.20.1701301036590.27354@namei.org>
Date: Mon, 30 Jan 2017 10:43:31 +1100 (AEDT)
From: James Morris <jmorris@...ei.org>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>
cc: SF Markus Elfring <elfring@...rs.sourceforge.net>,
linux-ima-devel@...ts.sourceforge.net,
linux-ima-user@...ts.sourceforge.net,
linux-security-module@...r.kernel.org,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
James Morris <james.l.morris@...cle.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 3/3] ima_fs: Move three error code assignments in
ima_write_policy()
On Fri, 27 Jan 2017, Mimi Zohar wrote:
> On Wed, 2017-01-25 at 10:34 +0100, SF Markus Elfring wrote:
> > From: Markus Elfring <elfring@...rs.sourceforge.net>
> > Date: Tue, 24 Jan 2017 22:47:07 +0100
> >
> > A local variable was set to an error code in three cases before a concrete
> > error situation was detected. Thus move the corresponding assignments into
> > if branches to indicate a software failure there.
> >
> > This issue was detected by using the Coccinelle software.
>
> This coding style was pretty common. I assume the compiler is smart
> enough to do the right thing. Is this a FYI, letting us know for the
> future the preferred coding style, or are we really upstreaming these
> sorts of coding style changes?
Nope, and I generally don't want cleanup patches from Markus going into
the security tree.
See also:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1254425.html
- James
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists