From: Arnd Bergmann <arnd@arndb.de>
To: Greg KH <gregkh@suse.de>
Cc: Tomoki Sekiyama <tomoki.sekiyama@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RESEND][BUG][PATCH]-rc: USB: yurex: add .llseek fop to file_operations
Date: Fri, 26 Nov 2010 16:22:28 +0100 [thread overview]
Message-ID: <201011261622.29100.arnd@arndb.de> (raw)
In-Reply-To: <20101125171613.GB18152@suse.de>
On Thursday 25 November 2010 18:16:13 Greg KH wrote:
> On Fri, Nov 26, 2010 at 01:11:05AM +0900, Tomoki Sekiyama wrote:
> > Hi Greg-KH,
> > Sorry for resending this; To: was not enough.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=23512
> >
> > Default llseek operation behavior was changed by the patch named
> > "vfs: make no_llseek the default" after the yurex driver was merged,
> > so the llseek to yurex is now ignored.
> >
> > This patch add llseek fop with default_llseek to yurex driver
> > to catch up to the change.
> >
> > Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@gmail.com>
>
> It's in my queue, sorry, been without power and water at home for a few
> days, will catch up on this stuff next week...
I was out most of the week, so I didn't get to look at it either.
Is there an actual bug here caused by having no .llseek function?
As far as I can tell, you don't really want to seek this file
anyway, so the default behaviour of disallowing llseek would actually
make more sense.
Arnd
next prev parent reply other threads:[~2010-11-26 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 16:11 [RESEND][BUG][PATCH]-rc: USB: yurex: add .llseek fop to file_operations Tomoki Sekiyama
2010-11-25 17:16 ` Greg KH
2010-11-26 15:22 ` Arnd Bergmann [this message]
2010-11-27 3:46 ` Tomoki Sekiyama
2010-11-29 15:04 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201011261622.29100.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tomoki.sekiyama@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox