[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D2RQC1H7N1JI.1W4JT8FI0R8L4@kernel.org>
Date: Wed, 17 Jul 2024 13:07:58 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "David Gstir" <david@...ma-star.at>, "sigma star Kernel Team"
<upstream+dcp@...ma-star.at>, "James Bottomley"
<James.Bottomley@...senPartnership.com>, "Mimi Zohar"
<zohar@...ux.ibm.com>, "David Howells" <dhowells@...hat.com>, "Paul Moore"
<paul@...l-moore.com>, "James Morris" <jmorris@...ei.org>, "Serge E.
Hallyn" <serge@...lyn.com>, "David Oberhollenzer"
<david.oberhollenzer@...ma-star.at>, "Richard Weinberger" <richard@....at>
Cc: <linux-integrity@...r.kernel.org>, <keyrings@...r.kernel.org>,
<linux-security-module@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
"kernel test robot" <lkp@...el.com>
Subject: Re: [PATCH 1/2] KEYS: trusted: fix DCP blob payload length
assignment
On Wed Jul 3, 2024 at 3:53 PM EEST, David Gstir wrote:
> The DCP trusted key type uses the wrong helper function to store
> the blob's payload length which can lead to the wrong byte order
> being used in case this would ever run on big endian architectures.
>
> Fix by using correct helper function.
>
> Signed-off-by: David Gstir <david@...ma-star.at>
> Suggested-by: Richard Weinberger <richard@....at>
You cannot suggest a change that you author yourself.
> Reported-by: kernel test robot <lkp@...el.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202405240610.fj53EK0q-lkp@intel.com/
> Fixes: 2e8a0f40a39c ("KEYS: trusted: Introduce NXP DCP-backed trusted keys")
Tags are in wrong order. For next round:
Cc: stable@...r.kernel.org # v6.10+
Fixes: 2e8a0f40a39c ("KEYS: trusted: Introduce NXP DCP-backed trusted keys")
Reported-by: kernel test robot <lkp@...el.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202405240610.fj53EK0q-lkp@intel.com/
Signed-off-by: David Gstir <david@...ma-star.at>
Signed-off-by: Jarkko Sakkinen <jarkko@...nel.org>
BR, Jarkko
Powered by blists - more mailing lists