All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
	cratiu@nvidia.com, dtatulea@nvidia.com, gal@nvidia.com,
	leon@kernel.org, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, mbloch@nvidia.com, saeedm@nvidia.com,
	horms@kernel.org
Subject: Re: [PATCH net] net/mlx5: Only set num_doorbells on a fully initialized SF
Date: Thu, 29 Oct 2026 09:40:04 +0000	[thread overview]
Message-ID: <179326680482.1714515.15230223868854423149.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026084503.4122732-1-tariqt@nvidia.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 26 Oct 2026 10:45:03 +0200 you wrote:
> From: Cosmin Ratiu <cratiu@nvidia.com>
> 
> The validation for the num_doorbells devlink param rejects values
> greater than num_channels. For lightweight SFs, this ends up accessing
> a NULL priv->eq_table, leading to a crash.
> 
> Fix that by rejecting setting num_doorbells on uninitialized SFs.
> 
> [...]

Here is the summary with links:
  - [net] net/mlx5: Only set num_doorbells on a fully initialized SF
    https://git.kernel.org/netdev/net/c/fa503935c2d6

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-29  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  8:45 [PATCH net] net/mlx5: Only set num_doorbells on a fully initialized SF Tariq Toukan
2026-10-26  8:50 ` netdev-bot+sinfo
2026-10-26  9:35 ` sashiko-bot
2026-10-28 12:21 ` Daniel Machon
2026-10-29  9: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=179326680482.1714515.15230223868854423149.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@kernel.org \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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.