From: Robert Love <rml@novell.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Greg KH <gregkh@suse.de>,
Dmitry Torokhov <dtor_core@ameritech.net>,
linux-kernel@vger.kernel.org, Jean Delvare <khali@linux-fr.org>
Subject: Re: [RFC/PATCH 0/5] read/write on attribute w/o show/store should return -ENOSYS
Date: Thu, 28 Apr 2005 13:44:32 -0400 [thread overview]
Message-ID: <1114710272.6682.63.camel@betsy> (raw)
In-Reply-To: <20050428173744.GO23013@shell0.pdx.osdl.net>
On Thu, 2005-04-28 at 10:37 -0700, Chris Wright wrote:
> SuSv3 suggests EBADF, however we already do EINVAL at VFS for no write
> op. Although, returning 0 (i.e. wrote zero bytes) is still meaningful
> too.
I think EBADF implies that you opened the thing not for writing, and now
you are trying to write to it.
But my understanding of this problem is that the open is succeeding for
writes, but when the actual write is performed, the store fails (or does
not exist).
EIO makes sense for that. EACCESS less so, but still some.
Robert Love
next prev parent reply other threads:[~2005-04-28 17:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 5:30 [RFC/PATCH 0/5] read/write on attribute w/o show/store should return -ENOSYS Dmitry Torokhov
2005-04-28 5:31 ` [RFC/PATCH 1/5] sysfs: if show/store is missing " Dmitry Torokhov
2005-04-28 5:41 ` [RFC/PATCH 2/5] sysfs: (driver/base) " Dmitry Torokhov
2005-04-28 5:42 ` [RFC/PATCH 3/5] sysfs: (driver/pci) " Dmitry Torokhov
2005-04-28 5:43 ` [RFC/PATCH 4/5] sysfs: (driver/block) " Dmitry Torokhov
2005-04-28 5:44 ` [RFC/PATCH 5/5] sysfs: (rest) " Dmitry Torokhov
2005-04-28 17:26 ` [RFC/PATCH 0/5] read/write on attribute w/o show/store should " Greg KH
2005-04-28 17:37 ` Chris Wright
2005-04-28 17:44 ` Robert Love [this message]
2005-04-28 17:51 ` Dmitry Torokhov
2005-04-28 19:56 ` Richard B. Johnson
2005-04-28 20:08 ` Robert Love
2005-04-28 17:42 ` Robert Love
2005-04-29 6:22 ` [PATCH 1/5 (take 2)] sysfs: if show/store is missing return -EIO Dmitry Torokhov
2005-04-29 6:23 ` [PATCH 2/5 (take 2)] sysfs: (driver/base) " Dmitry Torokhov
2005-04-29 6:26 ` [PATCH 4/5 (take 2)] sysfs: (driver/block) " Dmitry Torokhov
2005-04-29 6:26 ` [PATCH 3/5 (take 2)] sysfs: (driver/pci) " Dmitry Torokhov
2005-04-29 6:27 ` [PATCH 5/5 (take 2)] sysfs: (rest) " Dmitry Torokhov
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=1114710272.6682.63.camel@betsy \
--to=rml@novell.com \
--cc=chrisw@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=gregkh@suse.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
/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