From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: menage@google.com, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Add MS_BIND_FLAGS mount flag
Date: Thu, 14 Feb 2008 18:33:02 -0500 [thread overview]
Message-ID: <1203031982.18860.60.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <E1JPmPw-0003au-SF@pomaz-ex.szeredi.hu>
On Thu, 2008-02-14 at 23:18 +0100, Miklos Szeredi wrote:
> I understand perfectly that this is what you want to do. And I'm
> saying that the following code snippet should do exactly the same,
> without having to add a new syscall:
>
> char tmpbuf[64];
> sprintf(tmpbuf, "/proc/self/fd/%i", fd);
> mount(dev_name, tmpbuf, type, flags, data);
>
> [ You could actually try to read people's responses, instead of
> immediately assuming they don't understand :-/ ]
I did read your reply, but the follow-link magic that is performed in
proc_fd_link() wasn't immediately obvious to someone who is unfamiliar
with that code. I understand where you're coming from now.
Anyhow, that does indeed look as if it will do what is needed for the
automounter.
Trond
prev parent reply other threads:[~2008-02-14 23:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 5:45 Paul Menage
2008-02-14 6:02 ` Christoph Hellwig
2008-02-14 15:22 ` Paul Menage
2008-02-14 15:23 ` Paul Menage
2008-02-14 8:30 ` Miklos Szeredi
2008-02-14 13:06 ` Trond Myklebust
2008-02-14 15:19 ` Paul Menage
2008-02-14 16:03 ` Miklos Szeredi
2008-02-14 16:13 ` Paul Menage
2008-02-14 17:31 ` Miklos Szeredi
2008-02-14 18:05 ` Paul Menage
2008-02-14 22:30 ` Miklos Szeredi
2008-02-14 16:26 ` Trond Myklebust
2008-02-14 17:39 ` Miklos Szeredi
2008-02-14 19:17 ` Trond Myklebust
2008-02-14 22:18 ` Miklos Szeredi
2008-02-14 23:33 ` Trond Myklebust [this message]
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=1203031982.18860.60.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.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®