From: patchwork-bot+netdevbpf@kernel.org
To: Petr Oros <poros@redhat.com>
Cc: donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
jacob.e.keller@intel.com, ast@fiberby.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ivecera@redhat.com, mschmidt@redhat.com
Subject: Re: [PATCH net] tools: ynl: fix string attribute length to include null terminator
Date: Tue, 28 Oct 2025 00:00:06 +0000 [thread overview]
Message-ID: <176160960676.1627277.6717105101420126529.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251024132438.351290-1-poros@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 24 Oct 2025 15:24:38 +0200 you wrote:
> The ynl_attr_put_str() function was not including the null terminator
> in the attribute length calculation. This caused kernel to reject
> CTRL_CMD_GETFAMILY requests with EINVAL:
> "Attribute failed policy validation".
>
> For a 4-character family name like "dpll":
> - Sent: nla_len=8 (4 byte header + 4 byte string without null)
> - Expected: nla_len=9 (4 byte header + 5 byte string with null)
>
> [...]
Here is the summary with links:
- [net] tools: ynl: fix string attribute length to include null terminator
https://git.kernel.org/netdev/net/c/65f9c4c58889
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:[~2025-10-28 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 13:24 [PATCH net] tools: ynl: fix string attribute length to include null terminator Petr Oros
2025-10-24 13:38 ` Ivan Vecera
2025-10-25 0:03 ` Jakub Kicinski
[not found] ` <CAPR2-9=UeTLfqWbfX+NcLef0BQ_xbKq7MJgt4YsjMi==FWZD-Q@mail.gmail.com>
2025-10-25 19:05 ` Zahari Doychev
2025-10-27 9:08 ` Ivan Vecera
2025-10-28 0:00 ` 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=176160960676.1627277.6717105101420126529.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@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;
as well as URLs for NNTP newsgroup(s).