[dpdk-stable] patch 'test: check zero socket memory as valid' has been queued to LTS release 18.11.1

Kevin Traynor ktraynor at redhat.com
Thu Feb 7 14:25:57 CET 2019


Hi,

FYI, your patch has been queued to LTS release 18.11.1

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 02/14/19. 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.

Thanks.

Kevin Traynor

---
>From 2e0185e8a962790f4adda67c9a3e6f9465fb6677 Mon Sep 17 00:00:00 2001
From: Ilya Maximets <i.maximets at samsung.com>
Date: Fri, 25 Jan 2019 10:55:58 +0300
Subject: [PATCH] test: check zero socket memory as valid

[ upstream commit 10d66cee5bf51bbd27d58b565b3340282e18ef07 ]

Dynamic memory mode allowes zero socket-mem because all the
required memory could be allocated on demand.

Fixes: 0a703f0f36c1 ("eal/linux: fix parsing zero socket memory and limits")

Reported-by: Shuai Zhu <shuaix.zhu at intel.com>
Signed-off-by: Ilya Maximets <i.maximets at samsung.com>
Reviewed-by: David Marchand <david.marchand at redhat.com>
Acked-by: Anatoly Burakov <anatoly.burakov at intel.com>
---
 test/test/test_eal_flags.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/test/test/test_eal_flags.c b/test/test/test_eal_flags.c
index e3a60c7ae..81e345b87 100644
--- a/test/test/test_eal_flags.c
+++ b/test/test/test_eal_flags.c
@@ -1159,5 +1159,5 @@ test_memory_flags(void)
 			"--file-prefix=" memtest, "-m", DEFAULT_MEM_SIZE};
 
-	/* invalid (zero) --socket-mem flag */
+	/* valid (zero) --socket-mem flag */
 	const char *argv2[] = {prgname, "-c", "10", "-n", "2",
 			"--file-prefix=" memtest, "--socket-mem=0,0,0,0"};
@@ -1257,6 +1257,6 @@ test_memory_flags(void)
 		return -1;
 	}
-	if (launch_proc(argv2) == 0) {
-		printf("Error - process run ok with invalid (zero) --socket-mem!\n");
+	if (launch_proc(argv2) != 0) {
+		printf("Error - process failed with valid (zero) --socket-mem!\n");
 		return -1;
 	}
-- 
2.19.0

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2019-02-07 13:19:56.758409525 +0000
+++ 0051-test-check-zero-socket-memory-as-valid.patch	2019-02-07 13:19:55.000000000 +0000
@@ -1,13 +1,14 @@
-From 10d66cee5bf51bbd27d58b565b3340282e18ef07 Mon Sep 17 00:00:00 2001
+From 2e0185e8a962790f4adda67c9a3e6f9465fb6677 Mon Sep 17 00:00:00 2001
 From: Ilya Maximets <i.maximets at samsung.com>
 Date: Fri, 25 Jan 2019 10:55:58 +0300
 Subject: [PATCH] test: check zero socket memory as valid
 
+[ upstream commit 10d66cee5bf51bbd27d58b565b3340282e18ef07 ]
+
 Dynamic memory mode allowes zero socket-mem because all the
 required memory could be allocated on demand.
 
 Fixes: 0a703f0f36c1 ("eal/linux: fix parsing zero socket memory and limits")
-Cc: stable at dpdk.org
 
 Reported-by: Shuai Zhu <shuaix.zhu at intel.com>
 Signed-off-by: Ilya Maximets <i.maximets at samsung.com>


More information about the stable mailing list