From: syzbot <syzbot+de8e83db70e8beedd556@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [net?] INFO: rcu detected stall in sys_socket
Date: Mon, 04 Dec 2023 18:10:11 -0800 [thread overview]
Message-ID: <0000000000000986fc060bb9bc3b@google.com> (raw)
In-Reply-To: <00000000000077c77f060b603f2d@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [net?] INFO: rcu detected stall in sys_socket
Author: eadavis@qq.com
please test rcu detected stall in sys_socket
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 18d46e76d7c2
diff --git a/net/sched/sch_taprio.c b/net/sched/sch_taprio.c
index 31a8252bd09c..4bc377120ea0 100644
--- a/net/sched/sch_taprio.c
+++ b/net/sched/sch_taprio.c
@@ -843,6 +843,7 @@ static struct sk_buff *taprio_dequeue(struct Qdisc *sch)
rcu_read_lock();
entry = rcu_dereference(q->current_entry);
+ rcu_read_unlock();
/* if there's no entry, it means that the schedule didn't
* start yet, so force all gates to be open, this is in
* accordance to IEEE 802.1Qbv-2015 Section 8.6.9.4.5
@@ -869,8 +870,6 @@ static struct sk_buff *taprio_dequeue(struct Qdisc *sch)
}
done:
- rcu_read_unlock();
-
return skb;
}
prev parent reply other threads:[~2023-12-05 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 15:24 [syzbot] [net?] INFO: rcu detected stall in sys_socket (10) syzbot
2023-11-30 16:11 ` Fwd: " Jamal Hadi Salim
2023-11-30 19:01 ` Vinicius Costa Gomes
2023-12-01 0:12 ` Vinicius Costa Gomes
2023-12-01 19:02 ` Jamal Hadi Salim
2023-12-01 19:48 ` Eric Dumazet
2023-12-01 23:16 ` Vinicius Costa Gomes
2023-12-05 2:10 ` syzbot [this message]
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=0000000000000986fc060bb9bc3b@google.com \
--to=syzbot+de8e83db70e8beedd556@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.