From: Xiang Mei <xmei5@asu.edu>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, gregkh@linuxfoundation.org,
jhs@mojatatu.com, jiri@resnulli.us, security@kernel.org
Subject: Re: [PATCH v3] net/sched: sch_qfq: Fix race condition on qfq_aggregate
Date: Tue, 15 Jul 2025 15:16:29 -0700 [thread overview]
Message-ID: <aHbTPUYbroQ6W_1j@xps> (raw)
In-Reply-To: <aHaaQ1aSVt6vSQlT@pop-os.localdomain>
On Tue, Jul 15, 2025 at 11:13:23AM -0700, Cong Wang wrote:
> On Mon, Jul 14, 2025 at 05:09:42PM -0700, Xiang Mei wrote:
> >
> > Here is more information no how I tested:
> >
> > 1) I ran `python3 ./tdc.py -f ./tc-tests/infra/qdiscs.json -e 5e6d` 100
> > times
> > 2) The KASAN is enabled, and my patch is on it
> > 3) All 100 results show `ok 1 5e6d - Test QFQ's enqueue reentrant behaviour
> > with netem` without any crashing in dmesg
> >
> > I may need more information to trace this crash.
>
> Now I figured out why... It is all because of I used a wrong vmlinux to
> test this. Although I switched to vanilla -net branch, I forgot to
> rebuild the vmlinux which was still the one with my netem patches. And I
> just saw "netem duplicate 100%" in test case 5e6d, now it explains
> everything.
>
> Appologize for my stupid mistake here. I think it is clearly caused by
> my netem duplication patch (although the fix is not necessarily there).
>
> I will take care of this in my netem patchset.
>
> Sorry for the noise.
No worries, thanks for the explanations.
next prev parent reply other threads:[~2025-07-15 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 10:09 [PATCH v3] net/sched: sch_qfq: Fix race condition on qfq_aggregate Xiang Mei
2025-07-10 21:29 ` Cong Wang
2025-07-10 22:38 ` Xiang Mei
2025-07-13 21:31 ` Cong Wang
2025-07-13 21:34 ` Xiang Mei
2025-07-14 0:04 ` Xiang Mei
2025-07-14 22:32 ` Jakub Kicinski
2025-07-15 0:09 ` Xiang Mei
2025-07-15 17:23 ` Cong Wang
2025-07-15 18:13 ` Cong Wang
2025-07-15 22:16 ` Xiang Mei [this message]
2025-07-12 23:20 ` patchwork-bot+netdevbpf
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=aHbTPUYbroQ6W_1j@xps \
--to=xmei5@asu.edu \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=security@kernel.org \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).