From: patchwork-bot+netdevbpf@kernel.org
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: bpf@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
roberto.sassu@huawei.com
Subject: Re: bpf: fix key serial argument of bpf_lookup_user_key()
Date: Wed, 18 Jun 2025 01:20:28 +0000 [thread overview]
Message-ID: <175020962801.3757059.1481472277492875690.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <84cdb0775254d297d75e21f577089f64abdfbd28.camel@HansenPartnership.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 17 Jun 2025 10:57:36 -0400 you wrote:
> The underlying lookup_user_key() function uses a signed 32 bit integer
> for key serial numbers because legitimate serial numbers are positive
> (and > 3) and keyrings are negative. Using a u32 for the keyring in
> the bpf function doesn't currently cause any conversion problems but
> will start to trip the signed to unsigned conversion warnings when the
> kernel enables them, so convert the argument to signed (and update the
> tests accordingly) before it acquires more users.
>
> [...]
Here is the summary with links:
- bpf: fix key serial argument of bpf_lookup_user_key()
https://git.kernel.org/bpf/bpf-next/c/bd07bd12f2c1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-18 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 14:57 bpf: fix key serial argument of bpf_lookup_user_key() James Bottomley
2025-06-17 15:13 ` Roberto Sassu
2025-06-18 1:20 ` patchwork-bot+netdevbpf [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=175020962801.3757059.1481472277492875690.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bpf@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox