linux-kernel - Re: [PATCH] firewire: nosy: char device is not seekable

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]

Message-ID: <tkrat.74a48d50ea6be5f5@s5r6.in-berlin.de>
Date:	Wed, 13 Oct 2010 14:31:10 +0200 (CEST)
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	linux1394-devel@...ts.sourceforge.net
cc:	linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] firewire: nosy: char device is not seekable

Stefan Richter wrote:
>  static const struct file_operations nosy_ops = {
>  	.owner =		THIS_MODULE,
> +	.llseek =		no_llseek,
>  	.read =			nosy_read,
>  	.unlocked_ioctl =	nosy_ioctl,
>  	.poll =			nosy_poll,

PS; this is safe since the only client that uses this interface is
nosy-dump in linux/tools/firewire and it knows not to seek in this char
dev.
-- 
Stefan Richter
-=====-==-=- =-=- -==-=
http://arcgraph.de/sr/

--
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/