From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: Correct SuS compliance for open of large file without options
Date: Thu, 27 Sep 2007 16:19:12 +0100 [thread overview]
Message-ID: <20070927161912.2f08aff6@the-village.bc.nu> (raw)
In-Reply-To: <20070927150853.GA10154@kernel.dk>
> Well it's not my call, just seems like a really bad idea to change the
> error value. You can't claim full coverage for such testing anyway, it's
> one of those things that people will complain about two releases later
> saying it broke app foo.
Strange since we've spent years changing error values and getting them
right in the past.
There are real things to worry about - sysfs, sysfs, sysfs, ... and all
the other crap which is continually breaking stuff, not spec compliance
corrections that don't break things but move us into compliance with the
standard
Alan
next prev parent reply other threads:[~2007-09-27 15:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 13:29 Alan Cox
2007-09-27 14:01 ` Arjan van de Ven
2007-09-27 14:19 ` Alan Cox
2007-09-27 14:35 ` Jens Axboe
2007-09-27 14:44 ` Alan Cox
2007-09-27 15:08 ` Jens Axboe
2007-09-27 15:19 ` Alan Cox [this message]
2007-09-27 15:59 ` Theodore Tso
2007-09-27 17:23 ` Andrew Morton
2007-09-27 17:59 ` Greg KH
2007-09-27 18:37 ` Theodore Tso
2007-09-27 18:45 ` Matthew Wilcox
2007-09-27 21:34 ` Greg KH
2007-09-27 22:27 ` Kyle Moffett
2007-09-27 23:11 ` Greg KH
2007-09-27 23:19 ` Theodore Tso
2007-09-27 23:28 ` Matthew Wilcox
2007-09-28 2:21 ` Theodore Tso
2007-09-28 3:22 ` Greg KH
2007-09-28 3:21 ` Greg KH
2007-09-27 23:41 ` Jens Axboe
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=20070927161912.2f08aff6@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.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
all inboxes | Powered by JetHome®