From: patchwork-bot+netdevbpf@kernel.org
To: Xiang Mei <xmei5@asu.edu>
Cc: xiyou.wangcong@gmail.com, 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 null-deref in agg_dequeue
Date: Thu, 10 Jul 2025 09:20:06 +0000 [thread overview]
Message-ID: <175213920654.1416702.17199527229879667524.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250705212143.3982664-1-xmei5@asu.edu>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 5 Jul 2025 14:21:43 -0700 you wrote:
> To prevent a potential crash in agg_dequeue (net/sched/sch_qfq.c)
> when cl->qdisc->ops->peek(cl->qdisc) returns NULL, we check the return
> value before using it, similar to the existing approach in sch_hfsc.c.
>
> To avoid code duplication, the following changes are made:
>
> 1. Changed qdisc_warn_nonwc(include/net/pkt_sched.h) into a static
> inline function.
>
> [...]
Here is the summary with links:
- [v3] net/sched: sch_qfq: Fix null-deref in agg_dequeue
https://git.kernel.org/netdev/net/c/dd831ac8221e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-07-10 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM_iQpWkQd_1BdP+4cA2uQ5HP2wrb5dh8ZUgGWY7v3enLq_7Fg@mail.gmail.com>
2025-07-02 4:02 ` [PATCH] net/sched: sch_qfq: Fix null-deref in agg_dequeue Xiang Mei
2025-07-02 5:40 ` Greg KH
2025-07-02 7:18 ` Xiang Mei
2025-07-02 7:20 ` Xiang Mei
2025-07-02 7:32 ` Greg KH
2025-07-02 8:30 ` [PATCH v2] " Xiang Mei
2025-07-04 4:45 ` Cong Wang
2025-07-05 21:21 ` [PATCH v3] " Xiang Mei
2025-07-06 3:07 ` Cong Wang
2025-07-10 9:20 ` patchwork-bot+netdevbpf [this message]
2025-07-05 21:24 ` [PATCH v2] " Xiang Mei
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=175213920654.1416702.17199527229879667524.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).