* [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock
@ 2023-12-07 12:28 Chengfeng Ye
0 siblings, 0 replies; 4+ messages in thread
From: Chengfeng Ye @ 2023-12-07 12:28 UTC (permalink / raw)
To: 3chas3, davem, horms, kuba
Cc: linux-atm-general, netdev, linux-kernel, Chengfeng Ye
As &card->cli_queue_lock is acquired under softirq context along the
following call chain from solos_bh(), other acquisition of the same
lock inside process context should disable at least bh to avoid double
lock.
<deadlock #1>
console_show()
--> spin_lock(&card->cli_queue_lock)
<interrupt>
--> solos_bh()
--> spin_lock(&card->cli_queue_lock)
This flaw was found by an experimental static analysis tool I am
developing for irq-related deadlock.
To prevent the potential deadlock, the patch uses spin_lock_bh()
on the card->cli_queue_lock under process context code consistently
to prevent the possible deadlock scenario.
Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
---
drivers/atm/solos-pci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/atm/solos-pci.c b/drivers/atm/solos-pci.c
index 94fbc3abe60e..95f768b28a5e 100644
--- a/drivers/atm/solos-pci.c
+++ b/drivers/atm/solos-pci.c
@@ -449,9 +449,9 @@ static ssize_t console_show(struct device *dev, struct device_attribute *attr,
struct sk_buff *skb;
unsigned int len;
- spin_lock(&card->cli_queue_lock);
+ spin_lock_bh(&card->cli_queue_lock);
skb = skb_dequeue(&card->cli_queue[SOLOS_CHAN(atmdev)]);
- spin_unlock(&card->cli_queue_lock);
+ spin_unlock_bh(&card->cli_queue_lock);
if(skb == NULL)
return sprintf(buf, "No data.\n");
--
2.17.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock
@ 2023-12-07 12:34 Chengfeng Ye
2023-12-12 18:23 ` Jakub Kicinski
0 siblings, 1 reply; 4+ messages in thread
From: Chengfeng Ye @ 2023-12-07 12:34 UTC (permalink / raw)
To: 3chas3, davem, horms, kuba
Cc: linux-atm-general, netdev, linux-kernel, Chengfeng Ye
As &card->cli_queue_lock is acquired under softirq context along the
following call chain from solos_bh(), other acquisition of the same
lock inside process context should disable at least bh to avoid double
lock.
<deadlock #1>
console_show()
--> spin_lock(&card->cli_queue_lock)
<interrupt>
--> solos_bh()
--> spin_lock(&card->cli_queue_lock)
This flaw was found by an experimental static analysis tool I am
developing for irq-related deadlock.
To prevent the potential deadlock, the patch uses spin_lock_bh()
on the card->cli_queue_lock under process context code consistently
to prevent the possible deadlock scenario.
Fixes: 9c54004ea717 ("atm: Driver for Solos PCI ADSL2+ card.")
Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
---
V3: change to spin_lock_bh()
V2: add fix tag, and slipt into two patches
drivers/atm/solos-pci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/atm/solos-pci.c b/drivers/atm/solos-pci.c
index 94fbc3abe60e..95f768b28a5e 100644
--- a/drivers/atm/solos-pci.c
+++ b/drivers/atm/solos-pci.c
@@ -449,9 +449,9 @@ static ssize_t console_show(struct device *dev, struct device_attribute *attr,
struct sk_buff *skb;
unsigned int len;
- spin_lock(&card->cli_queue_lock);
+ spin_lock_bh(&card->cli_queue_lock);
skb = skb_dequeue(&card->cli_queue[SOLOS_CHAN(atmdev)]);
- spin_unlock(&card->cli_queue_lock);
+ spin_unlock_bh(&card->cli_queue_lock);
if(skb == NULL)
return sprintf(buf, "No data.\n");
--
2.17.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock
2023-12-07 12:34 [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock Chengfeng Ye
@ 2023-12-12 18:23 ` Jakub Kicinski
2023-12-12 18:26 ` Chengfeng Ye
0 siblings, 1 reply; 4+ messages in thread
From: Jakub Kicinski @ 2023-12-12 18:23 UTC (permalink / raw)
To: Chengfeng Ye
Cc: 3chas3, davem, horms, linux-atm-general, netdev, linux-kernel
On Thu, 7 Dec 2023 12:34:37 +0000 Chengfeng Ye wrote:
> As &card->cli_queue_lock is acquired under softirq context along the
> following call chain from solos_bh(), other acquisition of the same
> lock inside process context should disable at least bh to avoid double
> lock.
These appear to have been applied to net, thanks!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock
2023-12-12 18:23 ` Jakub Kicinski
@ 2023-12-12 18:26 ` Chengfeng Ye
0 siblings, 0 replies; 4+ messages in thread
From: Chengfeng Ye @ 2023-12-12 18:26 UTC (permalink / raw)
To: Jakub Kicinski
Cc: 3chas3, davem, horms, linux-atm-general, netdev, linux-kernel
Thanks much!
Best Regards,
Chengfeng
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-12-12 18:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-07 12:34 [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock Chengfeng Ye
2023-12-12 18:23 ` Jakub Kicinski
2023-12-12 18:26 ` Chengfeng Ye
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 12:28 Chengfeng Ye
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox