From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Jake Freeland <jfree@FreeBSD.org>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2 1/3] eal/freebsd: Do not use prev_ms_idx for hole detection
Date: Tue, 14 Oct 2025 11:06:31 +0200 [thread overview]
Message-ID: <17724fb4-337d-4300-b476-d4188f3814a9@intel.com> (raw)
In-Reply-To: <20250814213246.4141803-2-jfree@FreeBSD.org>
On 8/14/2025 11:32 PM, Jake Freeland wrote:
> Use rte_fbarray_is_used() to check if the previous fbarray entry is
> already empty.
>
> Using prev_ms_idx to do this is flawed in cases where we loop through
> multiple memseg lists. Each memseg list has its own count and length,
> so using a prev_ms_idx from one memseg list to check for used entries
> in another non-empty memseg list can lead to incorrect hole placement.
>
> Signed-off-by: Jake Freeland <jfree@FreeBSD.org>
> ---
> lib/eal/freebsd/eal_memory.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/lib/eal/freebsd/eal_memory.c b/lib/eal/freebsd/eal_memory.c
> index 6d3d46a390..be3bde2cb9 100644
> --- a/lib/eal/freebsd/eal_memory.c
> +++ b/lib/eal/freebsd/eal_memory.c
> @@ -103,7 +103,6 @@ rte_eal_hugepage_init(void)
> for (i = 0; i < internal_conf->num_hugepage_sizes; i++) {
> struct hugepage_info *hpi;
> rte_iova_t prev_end = 0;
> - int prev_ms_idx = -1;
> uint64_t page_sz, mem_needed;
> unsigned int n_pages, max_pages;
>
> @@ -167,9 +166,9 @@ rte_eal_hugepage_init(void)
> if (ms_idx < 0)
> continue;
>
> - if (need_hole && prev_ms_idx == ms_idx - 1)
> + if (need_hole &&
> + rte_fbarray_is_used(arr, ms_idx - 1))
> ms_idx++;
> - prev_ms_idx = ms_idx;
>
This is not a bug as the logic won't allow for this to happen, but some
static analysis tools might flag this:
Earlier we check for ms_idx < 0, so assuming ms_idx == 0, we will pass
(ms_idx - 1) to rte_fbarray_is_used. This won't actually happen because
ms_idx will never be 0 if `need_hole` is true, but *technically* it is
not impossible, and so should probably be addressed somehow to avoid
false positives from static analysis.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2025-10-14 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 21:32 [PATCH v2 0/3] EAL memory fixes Jake Freeland
2025-08-14 21:32 ` [PATCH v2 1/3] eal/freebsd: Do not use prev_ms_idx for hole detection Jake Freeland
2025-10-13 12:23 ` Burakov, Anatoly
2025-10-14 9:06 ` Burakov, Anatoly [this message]
2025-08-14 21:32 ` [PATCH v2 2/3] eal/freebsd: Avoid claiming memseg holes Jake Freeland
2025-10-13 12:36 ` Burakov, Anatoly
2025-10-13 13:12 ` Burakov, Anatoly
2025-08-14 21:32 ` [PATCH v2 3/3] eal/linux: Check hugepage access permissions Jake Freeland
2025-10-13 12:43 ` Burakov, Anatoly
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=17724fb4-337d-4300-b476-d4188f3814a9@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jfree@FreeBSD.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;
as well as URLs for NNTP newsgroup(s).