From: Zeeshan Ahmad <zeeshanahmad022019@gmail.com>
To: Sridhar Samudrala <sridhar.samudrala@intel.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, Simon Horman <horms@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Zeeshan Ahmad <zeeshanahmad022019@gmail.com>
Subject: [PATCH net-next v4] net: core: failover: enforce mandatory ops and clean up redundant checks
Date: Mon, 2 Mar 2026 11:43:17 +0500 [thread overview]
Message-ID: <20260302064317.9964-1-zeeshanahmad022019@gmail.com> (raw)
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.
Signed-off-by: Zeeshan Ahmad <zeeshanahmad022019@gmail.com>
---
v4:
- Harden failover_register() to forbid NULL ops as suggested by
Jakub Kicinski.
- Remove all redundant NULL checks for fops throughout the module.
- Remove the Fixes tag and target net-next, as this is now categorized
as a refactor/cleanup rather than a standalone bug fix.
v3:
- Move the fops NULL check to the top of the function before any
dereferences occur, as suggested by Dan Carpenter.
v2:
- Wrap the dereference in an if(fops) block instead of an early return
based on feedback from Simon Horman.
net/core/failover.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/net/core/failover.c b/net/core/failover.c
index 0eb2e0ec875b..11bb183c7a1b 100644
--- a/net/core/failover.c
+++ b/net/core/failover.c
@@ -59,7 +59,7 @@ static int failover_slave_register(struct net_device *slave_dev)
if (!failover_dev)
goto done;
- if (fops && fops->slave_pre_register &&
+ if (fops->slave_pre_register &&
fops->slave_pre_register(slave_dev, failover_dev))
goto done;
@@ -82,7 +82,7 @@ static int failover_slave_register(struct net_device *slave_dev)
slave_dev->priv_flags |= (IFF_FAILOVER_SLAVE | IFF_NO_ADDRCONF);
- if (fops && fops->slave_register &&
+ if (fops->slave_register &&
!fops->slave_register(slave_dev, failover_dev))
return NOTIFY_OK;
@@ -115,7 +115,7 @@ int failover_slave_unregister(struct net_device *slave_dev)
if (!failover_dev)
goto done;
- if (fops && fops->slave_pre_unregister &&
+ if (fops->slave_pre_unregister &&
fops->slave_pre_unregister(slave_dev, failover_dev))
goto done;
@@ -123,7 +123,7 @@ int failover_slave_unregister(struct net_device *slave_dev)
netdev_upper_dev_unlink(slave_dev, failover_dev);
slave_dev->priv_flags &= ~(IFF_FAILOVER_SLAVE | IFF_NO_ADDRCONF);
- if (fops && fops->slave_unregister &&
+ if (fops->slave_unregister &&
!fops->slave_unregister(slave_dev, failover_dev))
return NOTIFY_OK;
@@ -149,7 +149,7 @@ static int failover_slave_link_change(struct net_device *slave_dev)
if (!netif_running(failover_dev))
goto done;
- if (fops && fops->slave_link_change &&
+ if (fops->slave_link_change &&
!fops->slave_link_change(slave_dev, failover_dev))
return NOTIFY_OK;
@@ -174,7 +174,7 @@ static int failover_slave_name_change(struct net_device *slave_dev)
if (!netif_running(failover_dev))
goto done;
- if (fops && fops->slave_name_change &&
+ if (fops->slave_name_change &&
!fops->slave_name_change(slave_dev, failover_dev))
return NOTIFY_OK;
@@ -244,7 +244,7 @@ struct failover *failover_register(struct net_device *dev,
{
struct failover *failover;
- if (dev->type != ARPHRD_ETHER)
+ if (dev->type != ARPHRD_ETHER || !ops)
return ERR_PTR(-EINVAL);
failover = kzalloc_obj(*failover);
--
2.43.0
next reply other threads:[~2026-03-02 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 6:43 Zeeshan Ahmad [this message]
2026-03-04 2:10 ` [PATCH net-next v4] net: core: failover: enforce mandatory ops and clean up redundant checks patchwork-bot+netdevbpf
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=20260302064317.9964-1-zeeshanahmad022019@gmail.com \
--to=zeeshanahmad022019@gmail.com \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox