public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* lookup() on non-directories.
@ 2004-09-01 16:50 Frank van Maarseveen
  0 siblings, 0 replies; only message in thread
From: Frank van Maarseveen @ 2004-09-01 16:50 UTC (permalink / raw)
  To: linux-kernel

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-09-01 16:57 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-01 16:50 lookup() on non-directories Frank van Maarseveen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox