From: Jordi Pujol Palomer <jordipujolp@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux-Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fs/namei.c: Hard link and rename should check same device instead of same mount
Date: Sun, 20 Mar 2016 19:06:25 +0100 [thread overview]
Message-ID: <20160320190625.5e4ef31f@localdomain> (raw)
In-Reply-To: <20160316142516.GK17997@ZenIV.linux.org.uk>
El Wed, 16 Mar 2016 14:25:16 +0000
Al Viro <viro@ZenIV.linux.org.uk> escrigué:
> NAK. This is absolutely deliberate; moreover, mount --bind $DIR $DIR
> is often used just to set such a boundary.
It means that the way I have proposed may work also ?
Therefore we can develop a new option for binding to let the superuser
choose what is needed for every mount-bind, example:
mount --bind -o boundary $DIR $DIR
mount --bind -o noboundary $DIR1 $DIR2
and allow remount also,
mount -o remount,boundary $DIR
mount -o remount,noboundary $DIR
That seems feasible,
Jordi Pujol i Palomer
Enginyer Tècnic Industrial
next prev parent reply other threads:[~2016-03-20 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 13:05 [PATCH] fs/namei.c: Hard link and rename should check same device instead of same mount Jordi Pujol Palomer
2016-03-16 14:25 ` Al Viro
2016-03-20 18:06 ` Jordi Pujol Palomer [this message]
2016-03-20 18:22 ` Al Viro
2016-03-21 13:35 ` Jordi Pujol Palomer
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=20160320190625.5e4ef31f@localdomain \
--to=jordipujolp@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).