From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christoph Hellwig <hch@infradead.org>,
Pekka J Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@osdl.org>, Pekka Enberg <penberg@gmail.com>,
nathans@sgi.com, dtor_core@ameritech.net,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [PATCH] mm: return ENOBUFS instead of ENOMEM in generic_file_buffered_write
Date: Tue, 23 Aug 2005 08:50:32 -0500 [thread overview]
Message-ID: <d120d50005082306506fc9bd51@mail.gmail.com> (raw)
In-Reply-To: <20050823115559.GA6348@infradead.org>
On 8/23/05, Christoph Hellwig <hch@infradead.org> wrote:
> On Tue, Aug 23, 2005 at 11:46:33AM +0300, Pekka J Enberg wrote:
> > As noticed by Dmitry Torokhov, write() can not return ENOMEM:
> >
> > http://www.opengroup.org/onlinepubs/000095399/functions/write.html
> >
> > Therefore fixup generic_file_buffered_write() in mm/filemap.c (pointed out by
> > Nathan Scott).
>
> We had this discussion before, for EACCESS then. We've always been returning
> more errnos than SuS mentioned and Linus declared it's fine.
>
So does that mean that any error code is allowed? I would love to be
able to return ENODEV from a sysfs attribute if its device happens to
be removed in process. Is there a list of valid errnos for Linux that
supercedes SuS?
--
Dmitry
next prev parent reply other threads:[~2005-08-23 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11394.1124781401@kao2.melbourne.sgi.com>
2005-08-19 5:55 ` sysfs: write returns ENOMEM? Dmitry Torokhov
2005-08-19 7:29 ` Greg KH
2005-08-19 7:39 ` Pekka Enberg
2005-08-23 7:32 ` Nathan Scott
2005-08-23 7:55 ` Pekka Enberg
2005-08-23 8:28 ` Andrew Morton
2005-08-23 8:36 ` Pekka J Enberg
2005-08-23 8:46 ` [PATCH] mm: return ENOBUFS instead of ENOMEM in generic_file_buffered_write Pekka J Enberg
2005-08-23 11:55 ` Christoph Hellwig
2005-08-23 13:50 ` Dmitry Torokhov [this message]
2005-08-31 19:03 Steve French
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=d120d50005082306506fc9bd51@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=penberg@cs.helsinki.fi \
--cc=penberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.