From: patchwork-bot+netdevbpf@kernel.org
To: Jun Yang <juny24602@gmail.com>
Cc: xiyou.wangcong@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] sched: address a potential NULL pointer dereference in the GRED scheduler.
Date: Fri, 07 Mar 2025 00:50:32 +0000 [thread overview]
Message-ID: <174130863276.1835493.1039599542315128495.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250305154410.3505642-1-juny24602@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 5 Mar 2025 23:44:10 +0800 you wrote:
> If kzalloc in gred_init returns a NULL pointer, the code follows the
> error handling path, invoking gred_destroy. This, in turn, calls
> gred_offload, where memset could receive a NULL pointer as input,
> potentially leading to a kernel crash.
>
> Signed-off-by: Jun Yang <juny24602@gmail.com>
>
> [...]
Here is the summary with links:
- sched: address a potential NULL pointer dereference in the GRED scheduler.
https://git.kernel.org/netdev/net/c/115ef44a9822
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-03-07 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 16:04 [PATCH] sched: address a potential NULL pointer dereference in the GRED scheduler kwqcheii
2025-02-27 18:26 ` Cong Wang
2025-03-04 14:18 ` kwqcheii
2025-03-04 20:05 ` Cong Wang
2025-03-05 15:44 ` Jun Yang
2025-03-05 18:22 ` Cong Wang
2025-03-07 0:50 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-05 15:57 Jun Yang
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=174130863276.1835493.1039599542315128495.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=juny24602@gmail.com \
--cc=netdev@vger.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