public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Alexander Viro <viro@math.psu.edu>, Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: symlink_prefix
Date: Tue, 5 Jun 2001 14:43:02 +0200	[thread overview]
Message-ID: <20010605144302.A8058@bug.ucw.cz> (raw)
In-Reply-To: <UTC200106031053.MAA185287.aeb@vlet.cwi.nl> <Pine.GSO.4.21.0106030703590.27673-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0106030703590.27673-100000@weyl.math.psu.edu>; from Alexander Viro on Sun, Jun 03, 2001 at 07:25:25AM -0400

Hi!

> > What I did was: add a field  `char *mnt_symlink_prefix;'  to the
> > struct vfsmount, fill it in super.c:add_vfsmnt(), use it in
> > namei.c:vfs_follow_link(). Pick the value up by recognizing
> > in super.c:do_mount() the option "symlink_prefix=" before
> > giving the options to the separate filesystems.
> > 
> > [One could start a subdiscussion about that part. The mount(2)
> > system call needs to transport vfs information and per-fs information.
> > So far, the vfs information used flag bits only, but sooner or later
> > we'll want to have strings, and need a vfs_parse_mount_options().
> > Indeed, many filesystems today have uid= and gid= and umask= options
> > that might be removed from the individual filesystems and put into vfs.
> > After all, such options are also useful for (foreign) ext2 filesystems.]
> 
> _Please_, if we do anything of that kind - let's use a new syscall.
> Ideally, I'd say
> 	fs_fd = open("/fs/ext2", O_RDWR);
> 	/* error -> no such filesystem */
> 	write(fs_fd. "/dev/sda1", strlen("/dev/sda1"));
> 	/* error handling */
> 	write(fs_fd, "reserve=5", strlen(....));
> 	...
> 	dir = open("/usr/local", O_DIRECTORY);
> 	/* error handling */
> 	new_mount(dir, MNT_SET, fs_fd);	/* closes dir and fs_fd */
> 	/* error handling */
> 
> First open gives you a new channel. Preferably - wit datagram semantics (i.e.
> write() boundaries are preserved). Then you convince fs driver to give you
> fs. Then you mount it.

Looks good. Will it be possible to emulate old mount in libc in
(distant) future.
								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-06-06  9:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03 10:53 symlink_prefix Andries.Brouwer
2001-06-03 11:25 ` symlink_prefix Alexander Viro
2001-06-04 11:53   ` symlink_prefix Remi Turk
2001-06-05 12:43   ` Pavel Machek [this message]
2001-06-07  1:00   ` symlink_prefix Edgar Toernig
2001-06-07  1:19     ` symlink_prefix Alexander Viro
2001-06-07  3:43       ` symlink_prefix Edgar Toernig
  -- strict thread matches above, loose matches on Subject: below --
2001-06-04 12:28 symlink_prefix Hank Leininger
2001-06-05  2:31 ` symlink_prefix Ton Hospel
2001-06-03 17:37 symlink_prefix Andries.Brouwer
2001-06-03 16:36 symlink_prefix Andries.Brouwer
2001-06-03 17:19 ` symlink_prefix Alexander Viro
2001-06-04 22:05   ` symlink_prefix Albert D. Cahalan
2001-06-03 15:10 symlink_prefix Andries.Brouwer
2001-06-03 15:27 ` symlink_prefix Alexander Viro
2001-06-02 23:54 symlink_prefix Andries.Brouwer
2001-06-03  0:23 ` symlink_prefix Robert Love
2001-06-03  0:49 ` symlink_prefix Alexander Viro
2001-06-03  1:00   ` symlink_prefix Mitchell Blank Jr

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=20010605144302.A8058@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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