From: Aaron Brown <aaron.f.brown@intel.com>
To: davem@davemloft.net
Cc: Mark Rustad <mark.d.rustad@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
Aaron Brown <aaron.f.brown@intel.com>
Subject: [net-next 1/7] ixbge: Protect ixgbe_down with __IXGBE_DOWN bit
Date: Tue, 7 Jan 2014 23:40:41 -0800 [thread overview]
Message-ID: <1389166847-3780-2-git-send-email-aaron.f.brown@intel.com> (raw)
In-Reply-To: <1389166847-3780-1-git-send-email-aaron.f.brown@intel.com>
From: Mark Rustad <mark.d.rustad@intel.com>
The ixgbe_down function can now prevent multiple executions by
doing test_and_set_bit on __IXGBE_DOWN. This did not work before
introduction of the __IXGBE_REMOVED bit, because of overloading
of __IXGBE_DOWN. Also add smp_mb__before_clear_bit call before
clearing the __IXGBE_DOWN bit.
Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
Tested-by: Phil Schmitt <phillip.j.schmitt@intel.com>
Signed-off-by: Aaron Brown <aaron.f.brown@intel.com>
---
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
index cc06854..90a0b4a 100644
--- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
+++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
@@ -4572,6 +4572,7 @@ static void ixgbe_up_complete(struct ixgbe_adapter *adapter)
if (hw->mac.ops.enable_tx_laser)
hw->mac.ops.enable_tx_laser(hw);
+ smp_mb__before_clear_bit();
clear_bit(__IXGBE_DOWN, &adapter->state);
ixgbe_napi_enable_all(adapter);
@@ -4783,7 +4784,8 @@ void ixgbe_down(struct ixgbe_adapter *adapter)
int i;
/* signal that we are down to the interrupt handler */
- set_bit(__IXGBE_DOWN, &adapter->state);
+ if (test_and_set_bit(__IXGBE_DOWN, &adapter->state))
+ return; /* do nothing if already down */
/* disable receives */
rxctrl = IXGBE_READ_REG(hw, IXGBE_RXCTRL);
--
1.8.5.GIT
next prev parent reply other threads:[~2014-01-08 7:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 7:40 [net-next 0/7] Intel Wired LAN Driver Updates Aaron Brown
2014-01-08 7:40 ` Aaron Brown [this message]
2014-01-08 7:40 ` [net-next 2/7] ixgbe: Indicate removal state explicitly Aaron Brown
2014-01-08 8:37 ` Scott Feldman
2014-01-09 17:27 ` Rustad, Mark D
2014-01-09 18:18 ` Rustad, Mark D
2014-01-09 17:29 ` Rustad, Mark D
2014-01-08 7:40 ` [net-next 3/7] ixgbe: Use static inlines instead of macros Aaron Brown
2014-01-08 8:47 ` Scott Feldman
2014-01-09 17:34 ` Rustad, Mark D
2014-01-09 19:39 ` David Miller
2014-01-09 20:14 ` Rustad, Mark D
2014-01-09 20:19 ` David Miller
2014-01-09 20:46 ` Rustad, Mark D
2014-01-09 20:59 ` David Miller
2014-01-08 7:40 ` [net-next 4/7] ixgbe: Make ethtool register test use accessors Aaron Brown
2014-01-08 7:40 ` [net-next 5/7] ixgbe: Check register reads for adapter removal Aaron Brown
2014-01-08 8:35 ` Scott Feldman
2014-01-08 7:40 ` [net-next 6/7] ixgbe: Check for adapter removal on register writes Aaron Brown
2014-01-08 7:40 ` [net-next 7/7] ixgbe: Additional adapter removal checks Aaron Brown
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=1389166847-3780-2-git-send-email-aaron.f.brown@intel.com \
--to=aaron.f.brown@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=mark.d.rustad@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@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;
as well as URLs for NNTP newsgroup(s).