From: Linus Torvalds <torvalds@osdl.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@parcelfarce.linux.theplanet.co.uk, linux-kernel@vger.kernel.org
Subject: Re: open("foo", 3)
Date: Sat, 20 Aug 2005 10:30:23 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0508200958260.3317@g5.osdl.org> (raw)
In-Reply-To: <E1E6WCz-0005ym-00@dorka.pomaz.szeredi.hu>
On Sat, 20 Aug 2005, Miklos Szeredi wrote:
>
> My question is: is this deliberate or accidental? Wouldn't it be more
> logical to not require any permission to open such file? Or is there
> some security concern with that?
It's deliberate but historical. It's been a long time since I worked on
it, but it was meant for "special opens".
I _think_ it was used for things like "open block device without media
check" etc (we use O_NONBLOCK for that now), and it was used for directory
opens before we had O_DIRECTORY. (It's literally been years, so my
recollection may be bogus).
I don't think anything uses it any more, and it should probably be
deprecated rather than extended upon.
Linus
next prev parent reply other threads:[~2005-08-20 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 16:28 Miklos Szeredi
2005-08-20 17:30 ` Linus Torvalds [this message]
2005-08-20 18:00 ` Steven Rostedt
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=Pine.LNX.4.58.0508200958260.3317@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®