All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anirudh Virdi <avirdi@redhat.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, kees@kernel.org, horms@kernel.org,
	ast@fiberby.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: qede: initialize extack in qede_flow_spec_to_rule()
Date: Tue, 20 Oct 2026 19:40:17 +0000	[thread overview]
Message-ID: <179252521702.176933.4914190610931500796.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013105451.201211-1-avirdi@redhat.com>

Hello:

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

On Tue, 13 Oct 2026 16:24:51 +0530 you wrote:
> qede_flow_spec_to_rule() declares a netlink_ext_ack on the stack
> without initializing it. qede_parse_flow_attr() and
> qede_flow_spec_validate() only set extack._msg on error paths via
> NL_SET_ERR_MSG_MOD(), so on a successful parse the err_out block
> reads an uninitialized pointer. If that garbage happens to be
> non-NULL, DP_NOTICE("%s", extack._msg) dereferences it inside
> vsnprintf, causing a page fault and kernel panic.
> 
> [...]

Here is the summary with links:
  - [net] net: qede: initialize extack in qede_flow_spec_to_rule()
    https://git.kernel.org/netdev/net/c/106e562966a0

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



      parent reply	other threads:[~2026-10-20 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 10:54 [PATCH net] net: qede: initialize extack in qede_flow_spec_to_rule() Anirudh Virdi
2026-10-13 12:50 ` Asbjørn Sloth Tønnesen
2026-10-13 13:12   ` Ido Schimmel
2026-10-13 19:49 ` Daniel Machon
2026-10-20 19:40 ` 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=179252521702.176933.4914190610931500796.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@fiberby.net \
    --cc=avirdi@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kees@kernel.org \
    --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 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.