From: Jakub Kicinski <kuba@kernel.org>
To: Xiang Mei <xmei5@asu.edu>
Cc: security@kernel.org, netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us
Subject: Re: [PATCH net v2] net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset
Date: Mon, 5 Jan 2026 16:30:52 -0800 [thread overview]
Message-ID: <20260105163052.06bf29da@kernel.org> (raw)
In-Reply-To: <hvgvn5n45dla46vehvoi63frvkzk7s2wnpbi6l3mrbfl5njk2y@ttfv2gestxf2>
On Thu, 1 Jan 2026 18:35:06 -0700 Xiang Mei wrote:
> For the new version of patch, I attached the crash infomation decoded from
> scripts/decode_stacktrace.sh.
Please build your kernel with debug info and run it again.
scripts/decode_stacktrace.sh should annotate the stack trace
with line info, looks like it only decoded the asm for you.
--
pw-bot: cr
next prev parent reply other threads:[~2026-01-06 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 1:31 [PATCH net v2] net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset Xiang Mei
2026-01-02 1:35 ` Xiang Mei
2026-01-06 0:30 ` Jakub Kicinski [this message]
2026-01-06 3:32 ` Xiang Mei
2026-01-04 4:20 ` Cong Wang
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=20260105163052.06bf29da@kernel.org \
--to=kuba@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=security@kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=xmei5@asu.edu \
/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