linux-kernel - Re: [PATCH] staging: make new character devices nonseekable

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:	Sun, 26 Sep 2010 18:22:55 -0700
From:	Greg KH <greg@...ah.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: make new character devices nonseekable

On Sun, Sep 26, 2010 at 05:31:52PM +0200, Arnd Bergmann wrote:
> As a preparation for changing the default behaviour of llseek to no_llseek,
> every file_operations structure should have a .llseek operation.
> 
> There are three new instances in staging now, which can all be changed
> into no_llseek explicitly since the devices do not need to seek.
> 
> Add nonseekable_open where appropriate, to prevent pread/pwrite as well.
> 
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
>  bcm/Bcmchar.c                    |    3 +++
>  bcm/InterfaceInit.c              |    1 +
>  ft1000/ft1000-usb/ft1000_chdev.c |    2 ++
>  3 files changed, 6 insertions(+)

Odd, this patch breaks the build, what's up?

Hm, do I need to apply it to a recent Linus version?  My staging-next
tree is 2.6.36-rc2 based, do I need to update it?

thanks,

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/