linux-kernel - Re: [PATCH] staging: android: ashmem: lseek failed due to no FMODE

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

Date:   Thu, 9 Mar 2017 13:38:05 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     zhangshuxiaomi@...il.com
Cc:     arve@...roid.com, riandrews@...roid.com,
        devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
        zhangshuxiao <zhangshuxiao@...omi.com>
Subject: Re: [PATCH] staging: android: ashmem: lseek failed due to no
 FMODE_LSEEK.

On Wed, Mar 08, 2017 at 06:18:32PM +0800, zhangshuxiaomi@...il.com wrote:
> From: zhangshuxiao <zhangshuxiao@...omi.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@...omi.com>

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

thanks,

greg k-h