From 6f78a6651f2c64b3a931a347628cd23e06ea4d99 Mon Sep 17 00:00:00 2001 From: Bruce Richardson Date: Tue, 16 Dec 2014 15:03:50 +0000 Subject: [PATCH] app/test: check for mbuf allocation failure If mbuf allocation failed for whatever reason, we would get a NULL pointer exception in test_table_acl.c:test_pipeline_single_filter test case. We fix this by causing an early break out of the application loop. If we quit the test immediately we would leak any existing allocated mbufs, but by breaking instead, we allow the test to continue and clean up the mbufs already in the pipeline, while still having a test failure as the mbuf counts should not match. Signed-off-by: Bruce Richardson --- app/test/test_table_acl.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/app/test/test_table_acl.c b/app/test/test_table_acl.c index 0f2b57e0b2..e4e9b9cbba 100644 --- a/app/test/test_table_acl.c +++ b/app/test/test_table_acl.c @@ -513,6 +513,11 @@ test_pipeline_single_filter(int expected_count) struct rte_mbuf *mbuf; mbuf = rte_pktmbuf_alloc(pool); + if (mbuf == NULL) + /* this will cause test failure after cleanup + * of already enqueued mbufs, as the mbuf + * counts won't match */ + break; memset(rte_pktmbuf_mtod(mbuf, char *), 0x00, sizeof(struct ipv4_5tuple)); -- 2.20.1