[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168978602267.22183.12710540348045539494.git-patchwork-notify@kernel.org>
Date: Wed, 19 Jul 2023 17:00:22 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Menglong Dong <menglong8.dong@...il.com>
Cc: yhs@...com, davem@...emloft.net, dsahern@...nel.org,
ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, song@...nel.org, john.fastabend@...il.com,
kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com,
jolsa@...nel.org, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, imagedong@...cent.com, netdev@...r.kernel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
flyingpeng@...cent.com, dan.carpenter@...aro.org
Subject: Re: [PATCH bpf-next] bpf,
x86: initialize the variable "first_off" in save_args()
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Wed, 19 Jul 2023 19:03:30 +0800 you wrote:
> From: Menglong Dong <imagedong@...cent.com>
>
> As Dan Carpenter reported, the variable "first_off" which is passed to
> clean_stack_garbage() in save_args() can be uninitialized, which can
> cause runtime warnings with KMEMsan. Therefore, init it with 0.
>
> Fixes: 473e3150e30a ("bpf, x86: allow function arguments up to 12 for TRACING")
> Cc: Hao Peng <flyingpeng@...cent.com>
> Reported-by: Dan Carpenter <dan.carpenter@...aro.org>
> Closes: https://lore.kernel.org/bpf/09784025-a812-493f-9829-5e26c8691e07@moroto.mountain/
> Signed-off-by: Menglong Dong <imagedong@...cent.com>
>
> [...]
Here is the summary with links:
- [bpf-next] bpf, x86: initialize the variable "first_off" in save_args()
https://git.kernel.org/bpf/bpf-next/c/492e797fdab2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists