[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YfGtVk/HQjgl1zSS@iki.fi>
Date: Wed, 26 Jan 2022 22:21:42 +0200
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 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.
BR, Jarkko
Powered by blists - more mailing lists