[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000000000042ee27060b089aff@google.com>
Date: Sat, 25 Nov 2023 22:50:35 -0800
From: syzbot <syzbot+e18ac85757292b7baf96@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [syzbot] [net?] possible deadlock in sch_direct_xmit
For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org.
***
Subject: [net?] possible deadlock in sch_direct_xmit
Author: eadavis@...com
please test deadlock in sch_direct_xmit
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c
index 4195a4bc26ca..4605314e605e 100644
--- a/net/sched/sch_generic.c
+++ b/net/sched/sch_generic.c
@@ -338,8 +338,11 @@ bool sch_direct_xmit(struct sk_buff *skb, struct Qdisc *q,
if (likely(skb)) {
HARD_TX_LOCK(dev, txq, smp_processor_id());
- if (!netif_xmit_frozen_or_stopped(txq))
+ if (!netif_xmit_frozen_or_stopped(txq)) {
+ netif_tx_stop_queue(txq);
skb = dev_hard_start_xmit(skb, dev, txq, &ret);
+ netif_tx_start_queue(txq);
+ }
else
qdisc_maybe_clear_missed(q, txq);
Powered by blists - more mailing lists