patch 'common/mlx5: fix overlapping memory ranges' has been queued to stable release 24.11.9
luca.boccassi at gmail.com
luca.boccassi at gmail.com
Tue Oct 27 12:49:54 CET 2026
Hi,
FYI, your patch has been queued to stable release 24.11.9
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 10/29/26. So please
shout if anyone has objections.
Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.
Queued patches are on a temporary branch at:
https://github.com/bluca/dpdk-stable
This queued commit can be viewed at:
https://github.com/bluca/dpdk-stable/commit/ffdbe451e3f2ae76f5e9d8a13c3d3124fd658545
Thanks.
Luca Boccassi
---
>From ffdbe451e3f2ae76f5e9d8a13c3d3124fd658545 Mon Sep 17 00:00:00 2001
From: Viacheslav Ovsiienko <viacheslavo at nvidia.com>
Date: Tue, 21 Jul 2026 15:13:37 +0300
Subject: [PATCH] common/mlx5: fix overlapping memory ranges
[ upstream commit f718141d6c79da87b60c33811eb4897e8db6d387 ]
The mlx5 driver requires special objects named Memory Regions
(MR) to perform DMA operations with network data. The memory
pool(s) is used to provide memory and to cover pool addresses
the mlx5 PMD -pre-creates the appropriate MRs on Rx queue creation.
The pool memory can be non-contigous and split into segments.
The PMD created MRs on the page alignment segment boundaries
and it could cause the overlapping MRs (in case if the end
address of one segment is aligned to ceiling and the next
segment start address is aligned to the floor).
The MRs overlapping could cause the wrong MR fetching from the
cache for the mbufs in the overlapping area if the starting
mbuf address falls into overlapped area and raise the
hardware memory protection exception.
Fixes: 690b2a88c2f7 ("common/mlx5: add mempool registration facilities")
Signed-off-by: Viacheslav Ovsiienko <viacheslavo at nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski at nvidia.com>
---
drivers/common/mlx5/mlx5_common_mr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/common/mlx5/mlx5_common_mr.c b/drivers/common/mlx5/mlx5_common_mr.c
index 177255f308e..a7920b379e9 100644
--- a/drivers/common/mlx5/mlx5_common_mr.c
+++ b/drivers/common/mlx5/mlx5_common_mr.c
@@ -1501,7 +1501,7 @@ mlx5_get_mempool_ranges(struct rte_mempool *mp, bool is_extmem,
qsort(chunks, chunks_n, sizeof(chunks[0]), mlx5_range_compare_start);
contig_n = 1;
for (i = 1; i < chunks_n; i++)
- if (chunks[i - 1].end != chunks[i].start) {
+ if (chunks[i - 1].end < chunks[i].start) {
chunks[contig_n - 1].end = chunks[i - 1].end;
chunks[contig_n] = chunks[i];
contig_n++;
--
2.47.3
---
Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- - 2026-10-27 11:43:57.604271786 +0000
+++ 0100-common-mlx5-fix-overlapping-memory-ranges.patch 2026-10-27 11:43:53.630063039 +0000
@@ -1 +1 @@
-From f718141d6c79da87b60c33811eb4897e8db6d387 Mon Sep 17 00:00:00 2001
+From ffdbe451e3f2ae76f5e9d8a13c3d3124fd658545 Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit f718141d6c79da87b60c33811eb4897e8db6d387 ]
+
@@ -23 +24,0 @@
-Cc: stable at dpdk.org
@@ -32 +33 @@
-index aa2d5e88a4..e968e928a1 100644
+index 177255f308e..a7920b379e9 100644
@@ -35 +36 @@
-@@ -1504,7 +1504,7 @@ mlx5_get_mempool_ranges(struct rte_mempool *mp, bool is_extmem,
+@@ -1501,7 +1501,7 @@ mlx5_get_mempool_ranges(struct rte_mempool *mp, bool is_extmem,
More information about the stable
mailing list