From: patchwork-bot+netdevbpf@kernel.org
To: Hao Ge <hao.ge@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, gehao@kylinos.cn,
dan.carpenter@linaro.org
Subject: Re: [PATCH] selftests/bpf: Fix incorrect parameters in NULL pointer checking
Date: Wed, 28 Aug 2024 16:00:32 +0000 [thread overview]
Message-ID: <172486083229.1310856.14469889698346367573.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240820023622.29190-1-hao.ge@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 20 Aug 2024 10:36:22 +0800 you wrote:
> From: Hao Ge <gehao@kylinos.cn>
>
> Smatch reported the following warning:
> ./tools/testing/selftests/bpf/testing_helpers.c:455 get_xlated_program()
> warn: variable dereferenced before check 'buf' (see line 454)
>
> It seems correct,so let's modify it based on it's suggestion.
>
> [...]
Here is the summary with links:
- selftests/bpf: Fix incorrect parameters in NULL pointer checking
https://git.kernel.org/bpf/bpf-next/c/c264487e5410
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-28 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 2:36 [PATCH] selftests/bpf: Fix incorrect parameters in NULL pointer checking Hao Ge
2024-08-20 2:47 ` Hao Ge
2024-08-28 16:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-20 2:34 Hao Ge
2024-08-21 21:03 ` Yonghong Song
2024-08-21 21:50 ` Dan Carpenter
2024-08-21 22:07 ` Alexei Starovoitov
2024-08-21 22:31 ` Dan Carpenter
2024-08-23 7:12 ` Hao Ge
2024-08-23 7:04 ` Hao Ge
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=172486083229.1310856.14469889698346367573.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=gehao@kylinos.cn \
--cc=hao.ge@linux.dev \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox