From: Oliver Neukum <oliver@neukum.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.name>,
gregkh@suse.de, maneesh@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: error handling in sysfs, fill_read_buffer()
Date: Tue, 2 Jan 2007 16:38:49 +0100 [thread overview]
Message-ID: <200701021638.49726.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0701021024110.4122-100000@iolanthe.rowland.org>
Am Dienstag, 2. Januar 2007 16:26 schrieb Alan Stern:
> On Tue, 2 Jan 2007, Oliver Neukum wrote:
>
> > Hi,
> >
> > if a driver returns an error in fill_read_buffer(), the buffer will be
> > marked as filled. Subsequent reads will return eof. But there is
> > no data because of an error, not because it has been read.
> > Not marking the buffer filled is the obvious fix.
> >
> > Regards
> > Oliver
> >
> > Signed-off-by: Oliver Neukum <oliver@neukum.name>
> > --
> >
> > --- a/fs/sysfs/file.c 2006-12-24 05:00:32.000000000 +0100
> > +++ b/fs/sysfs/file.c 2007-01-01 15:03:14.000000000 +0100
> > @@ -70,7 +70,8 @@
> > * Allocate @buffer->page, if it hasn't been already, then call the
> > * kobject's show() method to fill the buffer with this attribute's
> > * data.
> > - * This is called only once, on the file's first read.
> > + * This is called only once, on the file's first read unless an error
> > + * is returned.
> > */
>
> I don't think this matches what people expect of sysfs. If a show method
> fails then the assumption is that the file cannot be read at all, so
> there's no point in trying to call the method again.
This would make handling ENOMEM very hard.
Regards
Oliver
next prev parent reply other threads:[~2007-01-02 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 7:48 Oliver Neukum
2007-01-02 15:26 ` Alan Stern
2007-01-02 15:38 ` Oliver Neukum [this message]
2007-01-02 15:47 ` Alan Stern
2007-01-02 15:53 ` Oliver Neukum
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=200701021638.49726.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=oliver@neukum.name \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®