linux-kernel - [PATCH] metag/kernel/stacktrace.c: Use current_stack_pointer instead of current

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1441445637-5385-1-git-send-email-gang.chen.5i5j@gmail.com>
Date:	Sat,  5 Sep 2015 17:33:57 +0800
From:	gang.chen.5i5j@...il.com
To:	james.hogan@...tec.com
Cc:	linux-metag@...r.kernel.org, linux-kernel@...r.kernel.org,
	gchen_5i5j@...n.com, Chen Gang <gang.chen.5i5j@...il.com>
Subject: [PATCH] metag/kernel/stacktrace.c: Use current_stack_pointer instead of current_sp

From: Chen Gang <gang.chen.5i5j@...il.com>

Since we have defined current_stack_pointer, current_sp is redudancy, so
remove it.

Signed-off-by: Chen Gang <gang.chen.5i5j@...il.com>
---
 arch/metag/kernel/stacktrace.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/arch/metag/kernel/stacktrace.c b/arch/metag/kernel/stacktrace.c
index 5510361..5db1176 100644
--- a/arch/metag/kernel/stacktrace.c
+++ b/arch/metag/kernel/stacktrace.c
@@ -165,11 +165,9 @@ void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace)
 		frame.pc = thread_saved_pc(tsk);
 #endif
 	} else {
-		register unsigned long current_sp asm ("A0StP");
-
 		data.no_sched_functions = 0;
 		frame.fp = (unsigned long)__builtin_frame_address(0);
-		frame.sp = current_sp;
+		frame.sp = current_stack_pointer;
 		frame.lr = (unsigned long)__builtin_return_address(0);
 		frame.pc = (unsigned long)save_stack_trace_tsk;
 	}
-- 
1.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/