Re: [PATCH] staging: android: ashmem: lseek failed due to no FMODE_LSEEK.

From	Greg KH <gregkh@linuxfoundation.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH] staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
Date	2017-03-09 13:40 +0100
Message-ID	<tj5wl-5a0-9@gated-at.bofh.it> (permalink)
References	<tiH0Z-5e8-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, Mar 08, 2017 at 06:18:32PM +0800, zhangshuxiaomi@gmail.com wrote:
> From: zhangshuxiao <zhangshuxiao@xiaomi.com>
> 
> vfs_llseek will check whether the file mode has
> FMODE_LSEEK, no return failure. But ashmem can be
> lseek, so add FMODE_LSEEK to ashmem file.

Really?  What is causing this failure?  I haven't heard from anyone else
about this issue, is there something different in your userspace
framework?

> 
> Signed-off-by: zhangshuxiao <zhangshuxiao@xiaomi.com>

I need a "full" name for a signed-off-by: please.

thanks,

greg k-h

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH] staging: android: ashmem: lseek failed due to no FMODE_LSEEK. zhangshuxiaomi@gmail.com - 2017-03-08 11:30 +0100
  Re: [PATCH] staging: android: ashmem: lseek failed due to no  FMODE_LSEEK. Greg KH <gregkh@linuxfoundation.org> - 2017-03-09 13:40 +0100

csiph-web