From: Shinas Rasheed <srasheed@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <hgani@marvell.com>, <sedara@marvell.com>, <vimleshk@marvell.com>,
<thaller@redhat.com>, <wizhao@redhat.com>, <kheib@redhat.com>,
<egallen@redhat.com>, <konguyen@redhat.com>, <horms@kernel.org>,
<einstein.xue@synaxg.com>, Shinas Rasheed <srasheed@marvell.com>,
Veerasenareddy Burru <vburru@marvell.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Satananda Burla <sburla@marvell.com>,
Abhijit Ayarekar <aayarekar@marvell.com>
Subject: [PATCH net v1 1/4] octeon_ep: fix race conditions in ndo_get_stats64
Date: Mon, 2 Dec 2024 23:21:27 -0800 [thread overview]
Message-ID: <20241203072130.2316913-2-srasheed@marvell.com> (raw)
In-Reply-To: <20241203072130.2316913-1-srasheed@marvell.com>
ndo_get_stats64() can race with ndo_stop(), which frees input and
output queue resources. Implement device state variable to protect
against such resource usage.
Fixes: 6a610a46bad1 ("octeon_ep: add support for ndo ops")
Signed-off-by: Shinas Rasheed <srasheed@marvell.com>
---
.../ethernet/marvell/octeon_ep/octep_main.c | 27 +++++++++++++++++++
.../ethernet/marvell/octeon_ep/octep_main.h | 8 ++++++
2 files changed, 35 insertions(+)
diff --git a/drivers/net/ethernet/marvell/octeon_ep/octep_main.c b/drivers/net/ethernet/marvell/octeon_ep/octep_main.c
index 549436efc204..872b4848027c 100644
--- a/drivers/net/ethernet/marvell/octeon_ep/octep_main.c
+++ b/drivers/net/ethernet/marvell/octeon_ep/octep_main.c
@@ -733,6 +733,7 @@ static int octep_open(struct net_device *netdev)
if (ret > 0)
octep_link_up(netdev);
+ set_bit(OCTEP_DEV_STATE_OPEN, &oct->state);
return 0;
set_queues_err:
@@ -745,6 +746,11 @@ static int octep_open(struct net_device *netdev)
return -1;
}
+static bool octep_drv_busy(struct octep_device *oct)
+{
+ return test_bit(OCTEP_DEV_STATE_READ_STATS, &oct->state);
+}
+
/**
* octep_stop() - stop the octeon network device.
*
@@ -759,6 +765,14 @@ static int octep_stop(struct net_device *netdev)
netdev_info(netdev, "Stopping the device ...\n");
+ clear_bit(OCTEP_DEV_STATE_OPEN, &oct->state);
+ /* Make sure device state open is cleared so that no more
+ * stats fetch can happen intermittently
+ */
+ smp_mb__after_atomic();
+ while (octep_drv_busy(oct))
+ msleep(20);
+
octep_ctrl_net_set_link_status(oct, OCTEP_CTRL_NET_INVALID_VFID, false,
false);
octep_ctrl_net_set_rx_state(oct, OCTEP_CTRL_NET_INVALID_VFID, false,
@@ -1001,6 +1015,16 @@ static void octep_get_stats64(struct net_device *netdev,
&oct->iface_rx_stats,
&oct->iface_tx_stats);
+ set_bit(OCTEP_DEV_STATE_READ_STATS, &oct->state);
+ /* Make sure read stats state is set, so that ndo_stop
+ * doesn't clear resources as they are read
+ */
+ smp_mb__after_atomic();
+ if (!test_bit(OCTEP_DEV_STATE_OPEN, &oct->state)) {
+ clear_bit(OCTEP_DEV_STATE_READ_STATS, &oct->state);
+ return;
+ }
+
tx_packets = 0;
tx_bytes = 0;
rx_packets = 0;
@@ -1022,6 +1046,7 @@ static void octep_get_stats64(struct net_device *netdev,
stats->rx_errors = oct->iface_rx_stats.err_pkts;
stats->collisions = oct->iface_tx_stats.xscol;
stats->tx_fifo_errors = oct->iface_tx_stats.undflw;
+ clear_bit(OCTEP_DEV_STATE_READ_STATS, &oct->state);
}
/**
@@ -1526,6 +1551,8 @@ static int octep_sriov_disable(struct octep_device *oct)
pci_disable_sriov(pdev);
CFG_GET_ACTIVE_VFS(oct->conf) = 0;
+ clear_bit(OCTEP_DEV_STATE_OPEN, &oct->state);
+
return 0;
}
diff --git a/drivers/net/ethernet/marvell/octeon_ep/octep_main.h b/drivers/net/ethernet/marvell/octeon_ep/octep_main.h
index fee59e0e0138..78293366e7de 100644
--- a/drivers/net/ethernet/marvell/octeon_ep/octep_main.h
+++ b/drivers/net/ethernet/marvell/octeon_ep/octep_main.h
@@ -223,6 +223,12 @@ struct octep_pfvf_info {
u32 mbox_version;
};
+/* Device state */
+enum octep_dev_state {
+ OCTEP_DEV_STATE_OPEN,
+ OCTEP_DEV_STATE_READ_STATS,
+};
+
/* The Octeon device specific private data structure.
* Each Octeon device has this structure to represent all its components.
*/
@@ -318,6 +324,8 @@ struct octep_device {
atomic_t hb_miss_cnt;
/* Task to reset device on heartbeat miss */
struct delayed_work hb_task;
+ /* Device state */
+ unsigned long state;
};
static inline u16 OCTEP_MAJOR_REV(struct octep_device *oct)
--
2.25.1
next prev parent reply other threads:[~2024-12-03 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 7:21 [PATCH net v1 0/4] Fix " Shinas Rasheed
2024-12-03 7:21 ` Shinas Rasheed [this message]
2024-12-04 2:23 ` [PATCH net v1 1/4] octeon_ep: fix " Jakub Kicinski
2024-12-03 7:21 ` [PATCH net v1 2/4] octeon_ep: remove firmware stats fetch " Shinas Rasheed
2024-12-03 7:21 ` [PATCH net v1 3/4] octeon_ep_vf: fix race conditions " Shinas Rasheed
2024-12-03 7:21 ` [PATCH net v1 4/4] octeon_ep_vf: remove firmware stats fetch " Shinas Rasheed
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=20241203072130.2316913-2-srasheed@marvell.com \
--to=srasheed@marvell.com \
--cc=aayarekar@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=egallen@redhat.com \
--cc=einstein.xue@synaxg.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=kheib@redhat.com \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=thaller@redhat.com \
--cc=vburru@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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
all inboxes | Powered by JetHome®