From: Lance Roy <ldr709@gmail•com>
To: linux-kernel@vger•kernel.org
Cc: "Paul E. McKenney" <paulmck@linux•ibm.com>,
Lance Roy <ldr709@gmail•com>,
Solarflare linux maintainers <linux-net-drivers@solarflare•com>,
Edward Cree <ecree@solarflare•com>,
Bert Kenward <bkenward@solarflare•com>,
"David S. Miller" <davem@davemloft•net>,
netdev@vger•kernel.org
Subject: [PATCH 06/16] sfc: Replace spin_is_locked() with lockdep
Date: Tue, 2 Oct 2018 22:38:52 -0700 [thread overview]
Message-ID: <20181003053902.6910-7-ldr709@gmail.com> (raw)
In-Reply-To: <20181003053902.6910-1-ldr709@gmail.com>
lockdep_assert_held() is better suited to checking locking requirements,
since it won't get confused when someone else holds the lock. This is
also a step towards possibly removing spin_is_locked().
Signed-off-by: Lance Roy <ldr709@gmail•com>
Cc: Solarflare linux maintainers <linux-net-drivers@solarflare•com>
Cc: Edward Cree <ecree@solarflare•com>
Cc: Bert Kenward <bkenward@solarflare•com>
Cc: "David S. Miller" <davem@davemloft•net>
Cc: <netdev@vger•kernel.org>
---
drivers/net/ethernet/sfc/efx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/sfc/efx.c b/drivers/net/ethernet/sfc/efx.c
index 330233286e78..f40c3d5ca413 100644
--- a/drivers/net/ethernet/sfc/efx.c
+++ b/drivers/net/ethernet/sfc/efx.c
@@ -3193,7 +3193,7 @@ struct hlist_head *efx_rps_hash_bucket(struct efx_nic *efx,
{
u32 hash = efx_filter_spec_hash(spec);
- WARN_ON(!spin_is_locked(&efx->rps_hash_lock));
+ lockdep_assert_held(&efx->rps_hash_lock);
if (!efx->rps_hash_table)
return NULL;
return &efx->rps_hash_table[hash % EFX_ARFS_HASH_TABLE_SIZE];
--
2.19.0
next prev parent reply other threads:[~2018-10-03 5:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181003053902.6910-1-ldr709@gmail.com>
2018-10-03 5:38 ` [PATCH 04/16] i40e: Replace spin_is_locked() with lockdep Lance Roy
2018-10-04 18:56 ` [Intel-wired-lan] " Bowers, AndrewX
2018-10-03 5:38 ` [PATCH 05/16] igbvf: " Lance Roy
2018-10-13 0:11 ` Brown, Aaron F
2018-10-03 5:38 ` Lance Roy [this message]
2018-10-03 5:38 ` [PATCH 07/16] smsc: " Lance Roy
2018-10-03 5:38 ` [PATCH 08/16] wireless: " Lance Roy
2018-10-03 9:06 ` Kalle Valo
2018-10-04 6:57 ` Lance Roy
2018-10-04 10:05 ` Kalle Valo
2018-10-05 8:35 ` [PATCH 08/16] zd1211rw: " Kalle Valo
2018-10-03 5:39 ` [PATCH 14/16] netfilter: " Lance Roy
2018-10-03 8:29 ` Jozsef Kadlecsik
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=20181003053902.6910-7-ldr709@gmail.com \
--to=ldr709@gmail$(echo .)com \
--cc=bkenward@solarflare$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ecree@solarflare$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-net-drivers@solarflare$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulmck@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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