linux-kernel - [PATCH] xtensa: Fix execdomain removal

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 11 Apr 2015 19:19:51 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Richard Weinberger <richard@....at>
Cc:	Chris Zankel <chris@...kel.net>, Max Filippov <jcmvbkbc@...il.com>,
	linux-xtensa@...ux-xtensa.org, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>
Subject: [PATCH] xtensa: Fix execdomain removal

The removal of exexdomain changes pointer offsets into the thread_info
structure.

Signed-off-by: Guenter Roeck <linux@...ck-us.net>
---
Applies on top of Richard's execdomain removal patches.
Tested with xtensa qemu session.

 arch/xtensa/include/asm/thread_info.h | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/arch/xtensa/include/asm/thread_info.h b/arch/xtensa/include/asm/thread_info.h
index d120278073b5..b3680a4738cd 100644
--- a/arch/xtensa/include/asm/thread_info.h
+++ b/arch/xtensa/include/asm/thread_info.h
@@ -64,12 +64,11 @@ struct thread_info {
 
 /* offsets into the thread_info struct for assembly code access */
 #define TI_TASK		 0x00000000
-#define TI_EXEC_DOMAIN	 0x00000004
-#define TI_FLAGS	 0x00000008
-#define TI_STATUS	 0x0000000C
-#define TI_CPU		 0x00000010
-#define TI_PRE_COUNT	 0x00000014
-#define TI_ADDR_LIMIT	 0x00000018
+#define TI_FLAGS	 0x00000004
+#define TI_STATUS	 0x00000008
+#define TI_CPU		 0x0000000C
+#define TI_PRE_COUNT	 0x00000010
+#define TI_ADDR_LIMIT	 0x00000014
 
 #endif
 
-- 
2.1.0

--
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/