From: patchwork-bot+netdevbpf@kernel.org
To: Zeeshan Ahmad <zeeshanahmad022019@gmail.com>
Cc: sridhar.samudrala@intel.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, edumazet@google.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, horms@kernel.org,
dan.carpenter@linaro.org
Subject: Re: [PATCH net-next v4] net: core: failover: enforce mandatory ops and clean up redundant checks
Date: Wed, 04 Mar 2026 02:10:06 +0000 [thread overview]
Message-ID: <177259020680.1558550.9680037756049177814.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302064317.9964-1-zeeshanahmad022019@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 2 Mar 2026 11:43:17 +0500 you wrote:
> The failover framework requires 'ops' to be functional. Currently,
> failover_register() allows an instance to be registered with NULL
> ops, which leads to inconsistent NULL checks and potential NULL
> pointer dereferences in the slave registration paths.
>
> Harden the entry point by requiring non-NULL ops in
> failover_register(). This ensures the 'fops' pointer is guaranteed
> to be valid for any successfully registered failover instance.
> Consequently, remove the now redundant NULL checks for 'fops'
> throughout the module to simplify the logic.
>
> [...]
Here is the summary with links:
- [net-next,v4] net: core: failover: enforce mandatory ops and clean up redundant checks
https://git.kernel.org/netdev/net-next/c/d6ca199568c5
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-03-04 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 6:43 [PATCH net-next v4] net: core: failover: enforce mandatory ops and clean up redundant checks Zeeshan Ahmad
2026-03-04 2:10 ` 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=177259020680.1558550.9680037756049177814.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@intel.com \
--cc=zeeshanahmad022019@gmail.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.