tests/kernel/lifo/lifo_api: Don't reuse name for different thread stacks

A limitation on current HW shadow stack implementation for x86 is that
more than one thread stack can't share the same variable name, even if
they are static. To avoid skipping useful tests, for now, while this
limitation holds, change the name of the stack variable.

Signed-off-by: Ederson de Souza <ederson.desouza@intel.com>

Author: edersondisouza

tests/kernel/lifo/lifo_api/src/test_lifo_contexts.c

@@ -14,7 +14,7 @@ K_LIFO_DEFINE(klifo);
 struct k_lifo lifo;
 static ldata_t data[LIST_LEN];
 
-static K_THREAD_STACK_DEFINE(tstack, STACK_SIZE);
+static K_THREAD_STACK_DEFINE(tstack_contexts, STACK_SIZE);
 static struct k_thread tdata;
 static struct k_sem end_sema;
 
@@ -59,7 +59,7 @@ static void tlifo_thread_thread(struct k_lifo *plifo)
 {
 	k_sem_init(&end_sema, 0, 1);
 	/**TESTPOINT: thread-thread data passing via lifo*/
-	k_tid_t tid = k_thread_create(&tdata, tstack, STACK_SIZE,
+	k_tid_t tid = k_thread_create(&tdata, tstack_contexts, STACK_SIZE,
 		tThread_entry, plifo, NULL, NULL,
 		K_PRIO_PREEMPT(0), 0, K_NO_WAIT);
 	tlifo_put(plifo);

tests/kernel/lifo/lifo_api/src/test_lifo_loop.c

@@ -12,7 +12,7 @@
 
 static ldata_t data[LIST_LEN];
 static struct k_lifo lifo;
-static K_THREAD_STACK_DEFINE(tstack, STACK_SIZE);
+static K_THREAD_STACK_DEFINE(tstack_loop, STACK_SIZE);
 static struct k_thread tdata;
 static struct k_sem end_sema;
 
@@ -60,7 +60,7 @@ static void tlifo_read_write(struct k_lifo *plifo)
 {
 	k_sem_init(&end_sema, 0, 1);
 	/**TESTPOINT: thread-isr-thread data passing via lifo*/
-	k_tid_t tid = k_thread_create(&tdata, tstack, STACK_SIZE,
+	k_tid_t tid = k_thread_create(&tdata, tstack_loop, STACK_SIZE,
 		tThread_entry, plifo, NULL, NULL,
 		K_PRIO_PREEMPT(0), 0, K_NO_WAIT);