From: patchwork-bot+netdevbpf@kernel.org
To: Hui Peng <benquike@gmail.com>
Cc: jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/sched: ematch: check nla_put_nohdr() return value in tcf_em_tree_dump()
Date: Thu, 24 Sep 2026 02:20:17 +0000 [thread overview]
Message-ID: <179021641714.1281065.10384838349478970893.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260919210624.3030344-1-benquike@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 19 Sep 2026 21:06:24 +0000 you wrote:
> When tcf_em_tree_dump() was converted from the legacy rtnetlink
> `RTA_PUT_NOHDR` macro (which contained an implicit `goto
> rtattr_failure;`) to `nla_put_nohdr()`, the return value check on
> `nla_put_nohdr()` was omitted for container/simple matches and raw match
> payloads.
>
> If the netlink dump skb runs out of tailroom at `nla_put_nohdr()`, the
> error is silently ignored and `match_start->nla_len` is finalized
> without the match payload, emitting a malformed/truncated
> TCA_EMATCH_TREE_LIST attribute to userspace instead of returning `-1`
> via `nla_put_failure` so rtnetlink can reallocate and retry the dump.
>
> [...]
Here is the summary with links:
- net/sched: ematch: check nla_put_nohdr() return value in tcf_em_tree_dump()
https://git.kernel.org/netdev/net-next/c/528de6832b21
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:[~2026-09-24 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 21:06 Hui Peng
2026-09-24 2: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=179021641714.1281065.10384838349478970893.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=benquike@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®