linux-kernel - Re: [PATCH] libbpf: fix the incorrect reference to the memlock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <176167260776.2322783.18424488316564504145.git-patchwork-notify@kernel.org>
Date: Tue, 28 Oct 2025 17:30:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jianyun Gao <jianyungao89@...il.com>
Cc: linux-kernel@...r.kernel.org, andrii@...nel.org, eddyz87@...il.com,
 ast@...nel.org, daniel@...earbox.net, martin.lau@...ux.dev, song@...nel.org,
 yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
 sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, bpf@...r.kernel.org
Subject: Re: [PATCH] libbpf: fix the incorrect reference to the memlock_rlim
 variable in the comment.

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:

On Mon, 27 Oct 2025 11:20:08 +0800 you wrote:
> The variable "memlock_rlim_max" referenced in the comment does not exist.
> I think that the author probably meant the variable "memlock_rlim". So,
> correct it.
> 
> Signed-off-by: Jianyun Gao <jianyungao89@...il.com>
> ---
>  tools/lib/bpf/bpf.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Here is the summary with links:
  - libbpf: fix the incorrect reference to the memlock_rlim variable in the comment.
    https://git.kernel.org/bpf/bpf-next/c/54c134f379ee

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html