From: Frank van Maarseveen <frankvm@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: lookup() on non-directories.
Date: Wed, 1 Sep 2004 18:50:43 +0200 [thread overview]
Message-ID: <20040901165043.GA31757@janus> (raw)
The reiserfs4 and openat() discussion made me thinking. This is different:
* /dev/hda1 -> /dev/hda/1
=> /dev/hda/1 causes a lookup in the partition table of /dev/hda
* /dev/hda/1/. is a "root inode lookup" in the superblock inside /dev/hda/1: no
explicit mount/umount but just the usual refcounting. File system type? the
kernel already knows about this stuff: needed for mounting the root-fs.
/dev/hda/1 need not be a special file.
* /usr/X11R6/bin/xterm/... ?
Kernel has some knowledge about ELF (fs/binfmt_*) so this could mean
something.
So what's the concept?
lookup() on files are just _interpretations_ of the file based on
knowledge the kernel already has. Interpretations might require
access( , X_OK) == 0 for sanity (in addition to R_OK and/or W_OK).
This way, user mounts/automounter would no longer be a requirement for
the user in order to get access to the usual things like USB storage,
CDROM, DVD, or images of those.
yes I know, this does not address the samba or reiserfs4 issues: openat()
name space now becomes orthogonal.
--
Frank
reply other threads:[~2004-09-01 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040901165043.GA31757@janus \
--to=frankvm@xs4all.nl \
--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