From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH 1/3] net/ice: check for null before dereferencing
Date: Thu, 15 Jan 2026 10:41:36 +0000 [thread overview]
Message-ID: <aWjEYOd1-GEm8moW@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260115103824.1982220-2-ciara.loftus@intel.com>
On Thu, Jan 15, 2026 at 10:38:21AM +0000, Ciara Loftus wrote:
> When commiting a new Tx scheduler hierarchy we assume the user has
> created a root node. However if they have not, it leads to an invalid
> memory access. While this would be an invalid configuration by the user
> we should still prevent the invalid memory access from happening. Do so
> by ensuring the root node is non null before dereferencing.
>
> Fixes: 715d449a965b ("net/ice: enhance Tx scheduler hierarchy support")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2026-01-15 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 10:38 [PATCH 0/3] Ice Tx Scheduler Fixes Ciara Loftus
2026-01-15 10:38 ` [PATCH 1/3] net/ice: check for null before dereferencing Ciara Loftus
2026-01-15 10:41 ` Bruce Richardson [this message]
2026-01-15 10:38 ` [PATCH 2/3] net/ice: fix priority mode printing in Tx scheduler dump Ciara Loftus
2026-01-15 10:55 ` Bruce Richardson
2026-01-15 10:38 ` [PATCH 3/3] net/ice: re-enable strict priority on non-root levels Ciara Loftus
2026-01-15 10:42 ` Bruce Richardson
2026-01-16 14:33 ` [PATCH 0/3] Ice Tx Scheduler Fixes Bruce Richardson
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=aWjEYOd1-GEm8moW@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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