From: Al Viro <viro@ftp.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] open: O_DIRECTORY and O_CREAT together should fail
Date: Sat, 24 Sep 2005 08:01:50 +0100 [thread overview]
Message-ID: <20050924070150.GL7992@ftp.linux.org.uk> (raw)
In-Reply-To: <E1EJ3ib-0007V7-00@dorka.pomaz.szeredi.hu>
On Sat, Sep 24, 2005 at 08:41:05AM +0200, Miklos Szeredi wrote:
> > > Well yes. But I don't think anybody is using it, and if so they are
> > > clearly breaking the rules in man open(2):
> >
> > Be liberal in what you accept and all such... Everything else aside,
> > why bother?
>
> To conform to well defined semantics?
Well-defined is not exactly the word I'd use for that mess (example -
we still have the last remnant of ancient BSD idiocy in there; the last
case when dangling symlink is still traversed upon object creation,
everything else had been fixed since then).
And O_DIRECTORY is not the only flag that acquires or loses meaning
depending on O_CREAT - consider e.g. O_EXCL. It's a mess, of course,
but this mess is part of userland ABI. We tried to fix symlink idiocy,
BTW, on the assumption that nothing would be relying on it. Didn't
work...
next prev parent reply other threads:[~2005-09-24 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 14:45 [PATCH] open: O_DIRECTORY and O_CREAT together should fail Miklos Szeredi
2005-09-23 19:28 ` Andrew Morton
2005-09-24 5:52 ` Miklos Szeredi
2005-09-24 6:09 ` Al Viro
2005-09-24 6:41 ` Miklos Szeredi
2005-09-24 7:01 ` Al Viro [this message]
2005-09-24 7:43 ` Miklos Szeredi
2005-09-24 19:53 ` Kyle Moffett
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=20050924070150.GL7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.