public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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 07:01:18 -0700	[thread overview]
Message-ID: <20070927070118.2bd4792e@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070927142919.10b62f9b@the-village.bc.nu>

On Thu, 27 Sep 2007 14:29:19 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> The early LFS work that Linux uses favours EFBIG in various places.
> SuSv3 specifically uses EOVERFLOW for this as noted by Michael (Bug
> 7253)


isn't this an ABI change?
What's the gain for doing this ABI change?

  reply	other threads:[~2007-09-27 14:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 13:29 [PATCH] fs: Correct SuS compliance for open of large file without options Alan Cox
2007-09-27 14:01 ` Arjan van de Ven [this message]
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
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=20070927070118.2bd4792e@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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