[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhRxjJ3WMNc=vwkLKGDjSN8G=P9ykMkYg9dAJs3SaxVYYA@mail.gmail.com>
Date: Wed, 29 Mar 2023 10:19:14 -0400
From: Paul Moore <paul@...l-moore.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: kernel-janitors@...r.kernel.org, selinux@...r.kernel.org,
Christian Göttsche <cgzones@...glemail.com>,
Eric Paris <eparis@...isplace.org>,
Michal Orzel <michalorzel.eng@...il.com>,
Ondrej Mosnacek <omosnace@...hat.com>,
Ruiqi Gong <gongruiqi1@...wei.com>,
Stephen Smalley <stephen.smalley.work@...il.com>,
Xiu Jianfeng <xiujianfeng@...wei.com>, cocci@...ia.fr,
LKML <linux-kernel@...r.kernel.org>,
Ruiqi Gong <ruiqi.gong@...com>
Subject: Re: selinux: Adjust implementation of security_get_bools()
On Wed, Mar 29, 2023 at 1:20 AM Markus Elfring <Markus.Elfring@....de> wrote:
> >> Would you like to take advice from another information source
> >> better into account?
> >
> > In this case, I prefer what I suggested.
>
> What does hinder you to work with more jump labels for improved exception handling?
I'm the one who has the responsibility to fix bugs in the code when no
one else has the time or the desire, I'm also the one who shepherds
these changes up to Linus and argues for contentious changes which are
not popular outside the Linux Kernel security community. Having to do
this with patches that I find bothersome hinders me in ways which are
sometimes difficult to explain, but easy to understand if you've ever
been responsible for maintaining a significant code base.
--
paul-moore.com
Powered by blists - more mailing lists