From: Daniel Borkmann <daniel@iogearbox.net>
To: Yafang Shao <laoar.shao@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Graf <tgraf@suug.ch>, Paul McKenney <paulmck@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"open list:BPF [RINGBUF]" <bpf@vger.kernel.org>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH] net/cls_cgroup: Fix task_get_classid() during qdisc run
Date: Tue, 19 Aug 2025 14:42:07 +0200 [thread overview]
Message-ID: <7d2f3767-64c5-4efa-862b-f463751a03bb@iogearbox.net> (raw)
In-Reply-To: <20250819093737.60688-1-laoar.shao@gmail.com>
On 8/19/25 11:37 AM, Yafang Shao wrote:
> During recent testing with the netem qdisc to inject delays into TCP
> traffic, we observed that our CLS BPF program failed to function correctly
> due to incorrect classid retrieval from task_get_classid(). The issue
> manifests in the following call stack:
>
> bpf_get_cgroup_classid+5
> cls_bpf_classify+507
> __tcf_classify+90
> tcf_classify+217
> __dev_queue_xmit+798
> bond_dev_queue_xmit+43
> __bond_start_xmit+211
> bond_start_xmit+70
> dev_hard_start_xmit+142
> sch_direct_xmit+161
> __qdisc_run+102 <<<<< Issue location
> __dev_xmit_skb+1015
> __dev_queue_xmit+637
> neigh_hh_output+159
> ip_finish_output2+461
> __ip_finish_output+183
> ip_finish_output+41
> ip_output+120
> ip_local_out+94
> __ip_queue_xmit+394
> ip_queue_xmit+21
> __tcp_transmit_skb+2169
> tcp_write_xmit+959
> __tcp_push_pending_frames+55
> tcp_push+264
> tcp_sendmsg_locked+661
> tcp_sendmsg+45
> inet_sendmsg+67
> sock_sendmsg+98
> sock_write_iter+147
> vfs_write+786
> ksys_write+181
> __x64_sys_write+25
> do_syscall_64+56
> entry_SYSCALL_64_after_hwframe+100
>
> The problem occurs when multiple tasks share a single qdisc. In such cases,
> __qdisc_run() may transmit skbs created by different tasks. Consequently,
> task_get_classid() retrieves an incorrect classid since it references the
> current task's context rather than the skb's originating task.
>
> Given that dev_queue_xmit() always executes with bh disabled, we can safely
> use in_softirq() instead of in_serving_softirq() to properly identify the
> softirq context and obtain the correct classid.
>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Thomas Graf <tgraf@suug.ch>
> ---
> include/net/cls_cgroup.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/net/cls_cgroup.h b/include/net/cls_cgroup.h
> index 7e78e7d6f015..fc9e0617a73c 100644
> --- a/include/net/cls_cgroup.h
> +++ b/include/net/cls_cgroup.h
> @@ -63,7 +63,7 @@ static inline u32 task_get_classid(const struct sk_buff *skb)
> * calls by looking at the number of nested bh disable calls because
> * softirqs always disables bh.
> */
> - if (in_serving_softirq()) {
> + if (in_softirq()) {
> struct sock *sk = skb_to_full_sk(skb);
>
> /* If there is an sock_cgroup_classid we'll use that. */
Hm, essentially you only want to use the fallback method of retrieving cgroup from
the socket when the dev_queue_xmit() was triggered via ksoftirqd, rather than from
a process via syscall all the way into dev_queue_xmit(). It gets more fuzzy presumably
when skbs are queued somewhere and then some other kthread calls the dev_queue_xmit().
Looking at in_softirq(), the comment says "the following macros are deprecated and
should not be used in new code", see commit 15115830c887 ("preempt: Cleanup the
macro maze a bit"). Maybe Sebastian or Paul has input on whether in_softirq() is
still supposed to be used.
Side question, did you investigate where the skb->sk association got orphaned
somewhere along the way?
Thanks,
Daniel
next prev parent reply other threads:[~2025-08-19 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 9:37 Yafang Shao
2025-08-19 12:42 ` Daniel Borkmann [this message]
2025-08-19 13:26 ` Sebastian Andrzej Siewior
2025-08-19 13:51 ` Yafang Shao
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=7d2f3767-64c5-4efa-862b-f463751a03bb@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=tgraf@suug.ch \
--cc=willemb@google.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
all inboxes | Powered by JetHome®