From: Andi Kleen <ak@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: akpm@osdl.org, marcelo.tosatti@cyclades.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Drop O_LARGEFILE from F_GETFL for POSIX compliance
Date: Mon, 22 Mar 2004 08:09:12 +0100 [thread overview]
Message-ID: <20040322080912.1dc28fc1.ak@suse.de> (raw)
In-Reply-To: <405E900C.2070502@redhat.com>
On Sun, 21 Mar 2004 23:04:44 -0800
Ulrich Drepper <drepper@redhat.com> wrote:
> Andi Kleen wrote:
>
> > No, because O_LARGEFILE is not part of POSIX :-) (they use open64 etc.)
>
> What are you talking about? Neither O_LARGEFILE nor open64 is in POSIX.
> But both are in the LFS extensions.
>
> This whole change seems dubious at best. Who has argued that
> O_LARGEFILE mustn't be returned? I do not agree at all. If the test
> suite checks this the author must defend the position.
I complained to this to the Austin group people at that point
and Andrew Josey told me that the issue has been discussed and the comittee
ruled that the Linux behaviour was not compliant I didn't inquire about the details
(standardeese bores me), ask him himself.
> I suggest to not make any changes. It is perfectly OK to define new O_
> flags and the open() specification does not require that none of them
> must set implicitly.
Just the LSB test suite won't pass then.
-Andi
next prev parent reply other threads:[~2004-03-22 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 4:13 [PATCH] Drop O_LARGEFILE from F_GETFL for POSIX compliance Andi Kleen
2004-03-22 4:29 ` Nicholas Miell
2004-03-22 4:34 ` Andrea Arcangeli
2004-03-22 4:45 ` Andi Kleen
2004-03-22 5:07 ` Andrea Arcangeli
2004-03-22 5:39 ` Andrew Morton
2004-03-22 6:14 ` Andi Kleen
2004-03-22 7:04 ` Ulrich Drepper
2004-03-22 7:09 ` Andi Kleen [this message]
2004-03-22 7:08 ` Andrew Morton
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=20040322080912.1dc28fc1.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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.