linux-kernel - Re: [PATCH] staging: android: ashmem: Add support for 32bit ashmem calls in a 64bit kernel

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]

Date:	Tue, 5 Mar 2013 18:27:45 +0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Serban Constantinescu <serban.constantinescu@....com>
Cc:	linux-kernel@...r.kernel.org, kernel-team@...roid.com,
	arve@...roid.com, john.stultz@...aro.org, Dave.Butcher@....com
Subject: Re: [PATCH] staging: android: ashmem: Add support for 32bit ashmem
 calls in a 64bit kernel

On Tue, Mar 05, 2013 at 10:18:27AM +0000, Serban Constantinescu wrote:
> Android's shared memory subsystem, Ashmem, does not support calls from a
> 32bit userspace in a 64 bit kernel. This patch adds support for syscalls
> coming from a 32bit userspace in a 64bit kernel.
> 
> The patch has been successfully tested on ARMv8 AEM(64bit
> platform model) and Versatile Express A9(32bit platform).
> 
> Signed-off-by: Serban Constantinescu <serban.constantinescu@....com>
> ---
>  drivers/staging/android/ashmem.c |   22 +++++++++++++++++++++-
>  drivers/staging/android/ashmem.h |    6 ++++++
>  2 files changed, 27 insertions(+), 1 deletion(-)

Ok, what has changed from your previous version that I rejected that is
going to actually allow this to build?

Hint, you gotta tell me what version of the patch this is, and what
changed, otherwise I'll just assume this is a resend of the previous
patch and go ahead and delete it from my queue.

In fact, I might as well do that, now deleted :)

greg k-h
--
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/