From: Srish Srinivasan <ssrish@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, nayna@linux.ibm.com,
gjoyce@linux.ibm.com, ritesh.list@gmail.com,
sshegde@linux.ibm.com, linux-kernel@vger.kernel.org,
rnsastry@linux.ibm.com, ssrish@linux.ibm.com,
stable@vger.kernel.org
Subject: [PATCH 02/12] pseries/plpks: fix error code for wrapping key reads
Date: Wed, 23 Sep 2026 23:58:06 +0530 [thread overview]
Message-ID: <20260923182816.151451-3-ssrish@linux.ibm.com> (raw)
In-Reply-To: <20260923182816.151451-1-ssrish@linux.ibm.com>
PLPKS variables with the PLPKS_WRAPPINGKEY policy bit set are not
readable. Return -EPERM instead of -EINVAL in this case to better
reflect the access restriction being enforced.
Fixes: 133aa79e211d ("pseries/plpks: add HCALLs for PowerVM Key Wrapping Module")
Cc: stable@vger.kernel.org # 7.0
Signed-off-by: Srish Srinivasan <ssrish@linux.ibm.com>
Tested-by: R Nageswara Sastry <rnsastry@linux.ibm.com>
---
arch/powerpc/platforms/pseries/plpks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/pseries/plpks.c b/arch/powerpc/platforms/pseries/plpks.c
index 7e56b3dcacbc..ccf5765a907b 100644
--- a/arch/powerpc/platforms/pseries/plpks.c
+++ b/arch/powerpc/platforms/pseries/plpks.c
@@ -829,7 +829,7 @@ static int plpks_read_var(u8 consumer, struct plpks_var *var)
return -EINVAL;
if (var->policy & PLPKS_WRAPPINGKEY)
- return -EINVAL;
+ return -EPERM;
auth = construct_auth(consumer);
if (IS_ERR(auth))
--
2.52.0
next prev parent reply other threads:[~2026-09-23 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 18:28 [PATCH 00/12] Refactor and harden PLPKS code Srish Srinivasan
2026-09-23 18:28 ` [PATCH 01/12] pseries/plpks: fix error handling in plpks_read_var() Srish Srinivasan
2026-09-23 18:28 ` Srish Srinivasan [this message]
2026-09-23 18:28 ` [PATCH 03/12] pseries/plpks: validate input to plpks_signed_update_var() Srish Srinivasan
2026-09-23 18:28 ` [PATCH 04/12] pseries/plpks: clear sensitive PLPKS buffers Srish Srinivasan
2026-09-23 18:28 ` [PATCH 05/12] pseries/plpks: clear sensitive buffers in wrapping operations Srish Srinivasan
2026-09-23 18:28 ` [PATCH 06/12] pseries/plpks: clear signed update authentication buffer Srish Srinivasan
2026-09-23 18:28 ` [PATCH 07/12] pseries/plpks: clear SED key data after use Srish Srinivasan
2026-09-23 18:28 ` [PATCH 08/12] pseries/plpks: fix self-reference in plpks_var initializer Srish Srinivasan
2026-09-23 18:28 ` [PATCH 09/12] pseries/plpks: hide wrapping_features when unsupported Srish Srinivasan
2026-09-23 18:28 ` [PATCH 10/12] pseries/plpks: make narrowing conversions explicit Srish Srinivasan
2026-09-23 18:28 ` [PATCH 11/12] pseries/plpks: rename the default wrapping key macro Srish Srinivasan
2026-09-23 18:28 ` [PATCH 12/12] pseries/plpks: update PKS documentation and MAINTAINERS entry Srish Srinivasan
2026-10-12 3:31 ` [PATCH 00/12] Refactor and harden PLPKS code Madhavan Srinivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260923182816.151451-3-ssrish@linux.ibm.com \
--to=ssrish@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=gjoyce@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=rnsastry@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.