From: Jarkko Sakkinen <jarkko@kernel.org>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] keys: Remove return variable and length check to simplify user_read
Date: Wed, 4 Mar 2026 02:10:11 +0200 [thread overview]
Message-ID: <aad4Y7WFjHr8lRyC@kernel.org> (raw)
In-Reply-To: <20260228094447.869637-1-thorsten.blum@linux.dev>
On Sat, Feb 28, 2026 at 10:44:46AM +0100, Thorsten Blum wrote:
> In user_read(), remove the unnecessary return variable 'ret' and return
> ->datalen directly. Drop the redundant 'buflen > 0' check and use min()
> to determine the number of bytes to copy. No functional changes.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
Trivial cleanup commits with no function are not feasible. They only do
harm e.g., for backporting actual bug fixes.
> ---
> security/keys/user_defined.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/security/keys/user_defined.c b/security/keys/user_defined.c
> index 6f88b507f927..b53e063272c2 100644
> --- a/security/keys/user_defined.c
> +++ b/security/keys/user_defined.c
> @@ -171,20 +171,14 @@ EXPORT_SYMBOL_GPL(user_describe);
> long user_read(const struct key *key, char *buffer, size_t buflen)
> {
> const struct user_key_payload *upayload;
> - long ret;
>
> upayload = user_key_payload_locked(key);
> - ret = upayload->datalen;
>
> /* we can return the data as is */
> - if (buffer && buflen > 0) {
> - if (buflen > upayload->datalen)
> - buflen = upayload->datalen;
> + if (buffer)
> + memcpy(buffer, upayload->data, min(buflen, upayload->datalen));
>
> - memcpy(buffer, upayload->data, buflen);
> - }
> -
> - return ret;
> + return upayload->datalen;
> }
>
> EXPORT_SYMBOL_GPL(user_read);
> --
> Thorsten Blum <thorsten.blum@linux.dev>
> GPG: 1D60 735E 8AEF 3BE4 73B6 9D84 7336 78FD 8DFE EAD4
>
BR, Jarkko
prev parent reply other threads:[~2026-03-04 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 9:44 [PATCH] keys: Remove return variable and length check to simplify user_read Thorsten Blum
2026-03-04 0:10 ` Jarkko Sakkinen [this message]
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=aad4Y7WFjHr8lRyC@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=thorsten.blum@linux.dev \
/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.