From: Mark Lord <lkml@rtr.ca>
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: permit link(2) to work across --bind mounts ?
Date: Wed, 19 Dec 2007 21:06:24 -0500 [thread overview]
Message-ID: <4769CE20.5090307@rtr.ca> (raw)
In-Reply-To: <20071220013355.3900.qmail@science.horizon.com>
linux@horizon.com wrote:
>> Why does link(2) not support hard-linking across bind mount points
>> of the same underlying filesystem ?
>
> Whenever we get mount -r --bind working properly (which I use to place
> copies of necessary shared libraries inside chroot jails while allowing
> page cache sharing), this feature would break security.
..
No, that would still function exactly as it does today.
The alternate behaviour that is desired for non-chroot purposes
would be per-bind-mount, and would require a mount flag to activate.
Cheers
next prev parent reply other threads:[~2007-12-20 2:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 1:33 RFC: permit link(2) to work across --bind mounts ? linux
2007-12-20 2:06 ` Mark Lord [this message]
[not found] <9BTqk-2ck-31@gated-at.bofh.it>
[not found] ` <9BTJN-2Sv-21@gated-at.bofh.it>
[not found] ` <9BTTr-35L-13@gated-at.bofh.it>
2007-12-19 13:43 ` Bodo Eggert
2007-12-19 14:23 ` Al Viro
2007-12-19 15:42 ` Johannes Weiner
2007-12-19 16:44 ` Mark Lord
2007-12-20 20:55 ` Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2007-12-18 22:46 Mark Lord
2007-12-18 22:57 ` Mark Lord
2007-12-18 23:00 ` Al Viro
2007-12-18 23:14 ` Al Viro
2007-12-19 3:54 ` Mark Lord
2007-12-19 3:59 ` David Newall
2007-12-19 16:47 ` Mark Lord
2007-12-19 18:38 ` David Newall
2007-12-29 2:53 ` dean gaudet
2007-12-29 3:31 ` Jan Engelhardt
2007-12-29 6:02 ` dean gaudet
2007-12-29 6:48 ` Jan Engelhardt
2007-12-29 8:29 ` David Newall
2007-12-29 16:18 ` dean gaudet
2007-12-29 20:35 ` David Newall
2007-12-29 20:40 ` dean gaudet
2007-12-30 3:43 ` Valdis.Kletnieks
2007-12-30 3:55 ` dean gaudet
2007-12-27 3:43 ` Rogelio M. Serrano 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=4769CE20.5090307@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).