[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16ae3e51dc4eeb2b2e674b8ff1051ac315fa492c.camel@linux.ibm.com>
Date: Fri, 05 Jan 2024 09:59:14 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Coiby Xu <coxu@...hat.com>
Cc: linux-integrity@...r.kernel.org, itrymybest80@...tonmail.com,
Dmitry
Kasatkin <dmitry.kasatkin@...il.com>,
Paul Moore <paul@...l-moore.com>, James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
"open list:SECURITY SUBSYSTEM" <linux-security-module@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: Re: [PATCH] integrity: don't throw an error immediately when
failed to add a cert to the .machine keyring
On Fri, 2024-01-05 at 21:27 +0800, Coiby Xu wrote:
> On Tue, Jan 02, 2024 at 12:54:02PM -0500, Mimi Zohar wrote:
> >Hi Coiby,
>
> Hi Mimi,
>
> >
> >According to https://docs.kernel.org/process/submitting-patches.html,the
> summary line should be no more than 70 - 75 characters.
>
> Thanks for pointing me to this limit! How about
> integrity: eliminate harmless error "Problem loading X.509 certificate -126"
Still >75. How about the following?
integrity: eliminate unnecessary "Problem loading X.509 certificate" msg
Mimi
>
> >
> >On Wed, 2023-12-27 at 12:41 +0800, Coiby Xu wrote:
> >> Currently when the kernel fails to add a cert to the .machine keyring,
> >> it will throw an error immediately in the function integrity_add_key.
> >>
> >> Since the kernel will try adding to the .platform keyring next or throw
> >> an error (in the caller of integrity_add_key i.e. add_to_machine_keyring),
> >> so there is no need to throw an error immediately in integrity_add_key.
> >>
> >> Reported-by: itrymybest80@...tonmail.com
> >> Closes: https://bugzilla.redhat.com/show_bug.cgi?id=2239331
> >> Signed-off-by: Coiby Xu <coxu@...hat.com>
> >
> >Otherwise, the patch looks good.
>
> Thanks for reviewing the patch!
Powered by blists - more mailing lists