[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YhLxfHcCccNUAiIl@kernel.org>
Date: Mon, 21 Feb 2022 02:57:16 +0100
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Dave Kleikamp <dave.kleikamp@...cle.com>
Cc: linux-kernel@...r.kernel.org, Sumit Garg <sumit.garg@...aro.org>,
James Bottomley <jejb@...ux.ibm.com>,
Mimi Zohar <zohar@...ux.ibm.com>,
David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] KEYS: trusted: Avoid calling null function
trusted_key_exit
On Mon, Feb 07, 2022 at 11:40:23AM -0600, Dave Kleikamp wrote:
> On 1/26/22 2:21PM, Jarkko Sakkinen wrote:
> > On Wed, Jan 26, 2022 at 12:41:55PM -0600, Dave Kleikamp wrote:
> > > If one loads and unloads the trusted module, trusted_key_exit can be
> > > NULL. Call it through static_call_cond() to avoid a kernel trap.
> > >
> > > Fixes: 5d0682be3189 ("KEYS: trusted: Add generic trusted keys framework")
> > >
> > > Signed-off-by: Dave Kleikamp <dave.kleikamp@...cle.com>
> >
> > Please re-send with cc stable and the empty line removed and I'll pick it.
>
> I re-sent a v2, but haven't seen any response from you.
>
> I can send it again, or feel free to clean up those lines yourself.
>
> Thanks,
> Shaggy
I've applied the patch. Thank you, and apologies for the latency.
BR, Jarkko
Powered by blists - more mailing lists