All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Bhargava Chenna Marreddy <bhargava.marreddy@broadcom.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
	vsrama-krishna.nemani@broadcom.com, vikas.gupta@broadcom.com
Subject: Re: [PATCH net 0/4] bnge: Fix error-path and IRQ setup bugs in probe/open
Date: Wed, 07 Oct 2026 01:40:06 +0000	[thread overview]
Message-ID: <179133720678.2864088.7645471729072398785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005121704.227866-1-bhargava.marreddy@broadcom.com>

Hello:

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

On Mon,  5 Oct 2026 17:47:00 +0530 you wrote:
> Four independent fixes for existing bugs in the bnge driver's probe/open
> path:
> 
>  [1/4] Unwind bnge_alloc_core() incrementally to avoid a NULL deref when an
>        allocation fails.
>  [2/4] Require aux_msix + min vectors so nq_nr_rings cannot end up 0.
>  [3/4] Treat an irq_set_affinity_hint() failure as a warning, not an open
>        failure.
>  [4/4] Clear bd->netdev when bnge_netdev_alloc() fails so it does not
>        point at a freed net_device.
> 
> [...]

Here is the summary with links:
  - [net,1/4] bnge: fix NULL deref in bnge_alloc_core() on failure
    https://git.kernel.org/netdev/net-next/c/cc7a4a3138a4
  - [net,2/4] bnge: require NQ vectors beyond aux reservation
    https://git.kernel.org/netdev/net-next/c/f94521b9d407
  - [net,3/4] bnge: do not fail open if IRQ affinity hint fails
    https://git.kernel.org/netdev/net-next/c/dc9a69f4d853
  - [net,4/4] bnge: clear bd->netdev on allocation failure
    https://git.kernel.org/netdev/net-next/c/21162b65d468

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-07  1:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 12:17 [PATCH net 0/4] bnge: Fix error-path and IRQ setup bugs in probe/open Bhargava Marreddy
2026-10-05 12:17 ` [PATCH net 1/4] bnge: fix NULL deref in bnge_alloc_core() on failure Bhargava Marreddy
2026-10-05 12:17 ` [PATCH net 2/4] bnge: require NQ vectors beyond aux reservation Bhargava Marreddy
2026-10-05 12:17 ` [PATCH net 3/4] bnge: do not fail open if IRQ affinity hint fails Bhargava Marreddy
2026-10-05 12:17 ` [PATCH net 4/4] bnge: clear bd->netdev on allocation failure Bhargava Marreddy
2026-10-05 12:23 ` [PATCH net 0/4] bnge: Fix error-path and IRQ setup bugs in probe/open netdev-bot+sinfo
2026-10-05 12:42   ` Bhargava Chenna Marreddy
2026-10-05 12:57 ` Przemek Kitszel
2026-10-07  1: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=179133720678.2864088.7645471729072398785.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bhargava.marreddy@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavan.chebbi@broadcom.com \
    --cc=vikas.gupta@broadcom.com \
    --cc=vsrama-krishna.nemani@broadcom.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.