netdev - Re: [PATCH] ynl: ensure exact-len value is resolved

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <171564062893.28873.1783841297383261530.git-patchwork-notify@kernel.org>
Date: Mon, 13 May 2024 22:50:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Antonio Quartulli <a@...table.cc>
Cc: donald.hunter@...il.com, kuba@...nel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] ynl: ensure exact-len value is resolved

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Sat, 11 May 2024 01:22:02 +0200 you wrote:
> For type String and Binary we are currently usinig the exact-len
> limit value as is without attempting any name resolution.
> However, the spec may specify the name of a constant rather than an
> actual value, which would result in using the constant name as is
> and thus break the policy.
> 
> Ensure the limit value is passed to get_limit(), which will always
> attempt resolving the name before printing the policy rule.
> 
> [...]

Here is the summary with links:
  - ynl: ensure exact-len value is resolved
    https://git.kernel.org/netdev/net-next/c/ec8c25746e32

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html