All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: agaur@marvell.com, davem@davemloft.net, horms@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	wojciech.drewek@intel.com, andrew+netdev@lunn.ch,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	sgoutham@marvell.com
Subject: Re: [PATCH net] octeontx2-af: fix NULL deref in NIX TM tree debugfs read path
Date: Mon, 24 Aug 2026 18:40:09 +0000	[thread overview]
Message-ID: <178759680939.3058449.15538562043695507466.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260820050333.2606095-1-rkannoth@marvell.com>

Hello:

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

On Thu, 20 Aug 2026 10:33:33 +0530 you wrote:
> From: Anshumali Gaur <agaur@marvell.com>
> 
> rvu_dbg_nix_tm_tree_display() dereferences pfvf->sq_ctx without
> checking whether the SQ context has been allocated. Reading
> /sys/kernel/debug/octeontx2/nix/tm_tree for a NIX LF whose transmit
> queues are not set up triggers a kernel oops.
> 
> [...]

Here is the summary with links:
  - [net] octeontx2-af: fix NULL deref in NIX TM tree debugfs read path
    https://git.kernel.org/netdev/net/c/ec65631bd5ec

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



      reply	other threads:[~2026-08-24 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  5:03 [PATCH net] octeontx2-af: fix NULL deref in NIX TM tree debugfs read path Ratheesh Kannoth
2026-08-24 18: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=178759680939.3058449.15538562043695507466.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=agaur@marvell.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sgoutham@marvell.com \
    --cc=wojciech.drewek@intel.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.