linux-kernel - Re: [PATCH] ftrace: unify arch_syscall

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100122.173838.159363288.davem@davemloft.net>
Date:	Fri, 22 Jan 2010 17:38:38 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	heiko.carstens@...ibm.com
Cc:	rostedt@...dmis.org, vapier@...too.org,
	linux-kernel@...r.kernel.org, fweisbec@...il.com, mingo@...hat.com,
	brueckner@...ux.vnet.ibm.com, lethal@...ux-sh.org
Subject: Re: [PATCH] ftrace: unify arch_syscall_addr() implementations

From: Heiko Carstens <heiko.carstens@...ibm.com>
Date: Fri, 22 Jan 2010 17:37:00 +0100

> On Fri, Jan 22, 2010 at 09:36:17AM -0500, Steven Rostedt wrote:
>> I would not be too sure. s390 is very strange, and I would definitely
>> want to get an Ack from the arch maintainers first.
> 
> It's not a typo. The syscall table on s390 contains always 32 bit pointers
> since we know that the address of the function to be called is (way) below
> 4GB. So this saves us a few bytes.
> In addition this makes syscall patching done by some security modules a
> bit more difficult, since they would need to store a 64 bit pointer.
> That's because we make sure that module addresses are always above 4GB.

Sparc64 is the same way.
--
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/