From: Jake Freeland <jfree@FreeBSD.org>
To: Anatoly Burakov <anatoly.burakov@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: Jake Freeland <jfree@FreeBSD.org>, dev@dpdk.org
Subject: [PATCH v3 3/3] eal/linux: check hugepage access permissions
Date: Wed, 14 Jan 2026 18:31:29 +0900 [thread overview]
Message-ID: <20260114093140.3256584-4-jfree@FreeBSD.org> (raw)
In-Reply-To: <20260114093140.3256584-1-jfree@FreeBSD.org>
Currently, hugepage mountpoints will be used irrespective of permissions,
leading to potential EACCES errors during memory allocation. Fix this by
not using a mountpoint if we do not have read/write permissions on it.
Signed-off-by: Jake Freeland <jfree@FreeBSD.org>
---
lib/eal/linux/eal_hugepage_info.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/lib/eal/linux/eal_hugepage_info.c b/lib/eal/linux/eal_hugepage_info.c
index d47a19c56a..350c7d8cf6 100644
--- a/lib/eal/linux/eal_hugepage_info.c
+++ b/lib/eal/linux/eal_hugepage_info.c
@@ -260,6 +260,13 @@ get_hugepage_dir(uint64_t hugepage_sz, char *hugedir, int len)
continue;
}
+ if (access(splitstr[MOUNTPT], R_OK | W_OK) < 0) {
+ EAL_LOG(NOTICE,
+ "Skipping hugepage directory '%s': missing R/W permissions"
+ splitstr[MOUNTPT]);
+ continue;
+ }
+
/*
* If no --huge-dir option has been given, we're done.
*/
--
2.51.0
next prev parent reply other threads:[~2026-01-14 9:33 UTC|newest]
Thread overview: 20+ 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
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
2025-10-15 16:53 ` [PATCH v2 0/3] EAL memory fixes Thomas Monjalon
2026-01-14 6:37 ` Stephen Hemminger
2026-01-14 9:31 ` [PATCH v3 " Jake Freeland
2026-01-14 9:31 ` [PATCH v3 1/3] eal/freebsd: do not use prev_ms_idx for hole detection Jake Freeland
2026-01-14 9:31 ` [PATCH v3 2/3] eal/freebsd: avoid claiming memseg holes Jake Freeland
2026-01-14 9:31 ` Jake Freeland [this message]
2026-01-14 10:04 ` [PATCH v4] eal/linux: check hugepage access permissions Jake Freeland
2026-02-13 16:01 ` [PATCH v3 3/3] " David Marchand
2026-02-13 16:02 ` [PATCH v3 0/3] EAL memory fixes David Marchand
2026-01-23 5:09 ` [PATCH v2 " Stephen Hemminger
2026-01-23 17:43 ` Jake Freeland
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=20260114093140.3256584-4-jfree@FreeBSD.org \
--to=jfree@freebsd.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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