From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754168Ab0JMMba (ORCPT ); Wed, 13 Oct 2010 08:31:30 -0400 Received: from einhorn.in-berlin.de ([192.109.42.8]:50328 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753999Ab0JMMb3 (ORCPT ); Wed, 13 Oct 2010 08:31:29 -0400 X-Envelope-From: stefanr@s5r6.in-berlin.de Date: Wed, 13 Oct 2010 14:31:10 +0200 (CEST) From: Stefan Richter Subject: Re: [PATCH] firewire: nosy: char device is not seekable To: linux1394-devel@lists.sourceforge.net cc: linux-kernel@vger.kernel.org, Arnd Bergmann In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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/