From: patchwork-bot+netdevbpf@kernel.org
To: Thaison Phan <thaisonphan@google.com>
Cc: kuba@kernel.org, donald.hunter@gmail.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
gfengyuan@google.com, stani@google.com, ast@fiberby.net,
matttbe@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] update NULL pointer handling in generated code
Date: Tue, 11 Aug 2026 01:30:09 +0000 [thread overview]
Message-ID: <178641180939.287084.735844536020296651.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260807171500.7188-1-thaisonphan@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 7 Aug 2026 17:14:58 +0000 you wrote:
> This series fixes potential NULL pointer dereferences in YNL-generated C
> code during dump list freeing and memory allocation in parsing getters.
>
> Changes in v2:
> - Moved null check in dump list free to be separate from while loop
> - Updated allocation checks to only be for getters as setters will
> be handled in a separate patch.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] tools: ynl: check for null ptr on dump free
https://git.kernel.org/netdev/net-next/c/7c62c481bb43
- [v2,net-next,2/2] tools: ynl: check alloc fails in generated getter code
https://git.kernel.org/netdev/net-next/c/153f709c8639
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-08-11 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 17:14 [PATCH v2 net-next 0/2] update NULL pointer handling in generated code Thaison Phan
2026-08-07 17:14 ` [PATCH v2 net-next 1/2] tools: ynl: check for null ptr on dump free Thaison Phan
2026-08-07 17:15 ` [PATCH v2 net-next 2/2] tools: ynl: check alloc fails in generated getter code Thaison Phan
2026-08-11 1:30 ` 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=178641180939.287084.735844536020296651.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=gfengyuan@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stani@google.com \
--cc=thaisonphan@google.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.