From: Richard Henderson <rth@redhat.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: unregistered changes to the user<->kernel API
Date: Thu, 14 Jun 2001 10:32:49 -0700 [thread overview]
Message-ID: <20010614103249.A28852@redhat.com> (raw)
In-Reply-To: <20010614191219.A30567@athlon.random> <20010614191634.B30567@athlon.random> <20010614192122.C30567@athlon.random>
In-Reply-To: <20010614192122.C30567@athlon.random>; from andrea@suse.de on Thu, Jun 14, 2001 at 07:21:22PM +0200
On Thu, Jun 14, 2001 at 07:21:22PM +0200, Andrea Arcangeli wrote:
> Richard are you sure we can break O_NOFOLLOW and still expect the machine to
> boot?
[uses in glibc]
Yes, I saw those. What is the effect of O_NOFOLLOW? To not
follow symbolic links when opening the file. If you open a
regular file, in effect nothing happens. Moreover, if these
opens were not finding files now, the system wouldn't work.
So: the effect, I suppose, is (1) disabling some security
within glibc, and (2) making these accesses slower since they
will be considered O_DIRECT after the change.
Which doesn't seem that life-threatening to me.
r~
next prev parent reply other threads:[~2001-06-14 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 17:12 unregistered changes to the user<->kernel API Andrea Arcangeli
2001-06-14 17:16 ` Andrea Arcangeli
2001-06-14 17:21 ` Andrea Arcangeli
2001-06-14 17:32 ` Richard Henderson [this message]
2001-06-14 17:47 ` Andrea Arcangeli
2001-06-14 18:16 ` Andrea Arcangeli
2001-06-14 18:17 ` Richard Henderson
2001-06-14 18:10 ` Alexander Viro
2001-06-14 17:25 ` Jeff Garzik
2001-06-14 17:44 ` Andrea Arcangeli
2001-06-14 17:52 ` Jeff Garzik
2001-06-14 18:03 ` Andrea Arcangeli
2001-06-14 18:11 ` Alan Cox
2001-06-14 18:27 ` Andrea Arcangeli
2001-06-14 21:43 ` Albert D. Cahalan
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=20010614103249.A28852@redhat.com \
--to=rth@redhat.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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.