linux-kernel - RE: [PATCH] s390/compat: build error for large compat syscall args

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]

Date:	Thu, 21 Apr 2016 22:37:11 +0900
From:	Jungseung Lee <js07.lee@...sung.com>
To:	heiko.carstens@...ibm.com, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: RE: [PATCH] s390/compat: build error for large compat syscall args

Hello,

> s390/compat: build error for large compat syscall args
>
>   Enforce 32 bit types for all compat syscall argument types.
>
>   This way we can make sure that all arguments get correct sign
>   or zero extension. Otherwise incorrect code would be generated.
>
>   E.g. for a 'long' type the COMPAT_SYSCALL_DEFINE macro wouldn't
>   generate code that would cause sign extension of the passed in 32
>   bit user space parameter.
>   This can cause quite subtle bugs like e.g. the one that was fixed
>   with dfd948e32af2e "fs/compat: fix parameter handling for compat
>   readv/writev syscalls".

include/linux/compat.h
#ifndef __SC_DELOUSE
#define __SC_DELOUSE(t,v) ((t)(unsigned long)(v))
#endif

We couldn't make sure that all compat syscall arguments has 
32 bit types with default definition.
Is there any reason that this patch is only applied for s390?

Please let me know if I miss something. 

BR