From: patchwork-bot+netdevbpf@kernel.org
To: Xin Liu <liuxin350@huawei.com>
Cc: quentin@isovalent.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org,
kongweibin2@huawei.com, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@google.com, song@kernel.org, wuchangye@huawei.com,
xiesongyang@huawei.com, yanan@huawei.com, yhs@fb.com,
zhudi2@huawei.com
Subject: Re: [PATCH] libbpf:fix overrun in attribute iteration
Date: Fri, 30 Sep 2022 22:20:14 +0000 [thread overview]
Message-ID: <166457641483.5145.8427039204984502212.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220930090708.62394-1-liuxin350@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 30 Sep 2022 17:07:08 +0800 you wrote:
> I accidentally found that a change in commit 1045b03e07d8 ("netlink: fix
> overrun in attribute iteration") was not synchronized to the function
> `nla_ok` in tools/lib/bpf/nlattr.c, I think it is necessary to modify,
> this patch will do it.
>
> Signed-off-by: Xin Liu <liuxin350@huawei.com>
>
> [...]
Here is the summary with links:
- libbpf:fix overrun in attribute iteration
https://git.kernel.org/bpf/bpf-next/c/51e05a8cf8eb
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:[~2022-09-30 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 9:07 [PATCH] libbpf:fix overrun in attribute iteration Xin Liu
2022-09-30 22: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=166457641483.5145.8427039204984502212.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=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kongweibin2@huawei.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuxin350@huawei.com \
--cc=martin.lau@linux.dev \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=wuchangye@huawei.com \
--cc=xiesongyang@huawei.com \
--cc=yanan@huawei.com \
--cc=yhs@fb.com \
--cc=zhudi2@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 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.