From: Chris Mason <chris.mason@oracle.com>
To: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Deny sys_link across subvolumes.
Date: Thu, 12 Nov 2009 10:00:39 -0500 [thread overview]
Message-ID: <20091112150039.GD3196@think> (raw)
In-Reply-To: <4AFBB5D2.3060405@jp.fujitsu.com>
On Thu, Nov 12, 2009 at 04:14:26PM +0900, TARUISI Hiroaki wrote:
>
> From: Christian Parpart <trapni@gentoo.org>
>
> I rebased Christian Parpart's patch to deny hard link across
> subvolumes. Original patch modifies also btrfs_rename, but
> I excluded it because we can move across subvolumes now and
> it make no problem.
Thanks for sending this in again.
Actually, we still can't rename across subvolumes, but we do support
renaming subvolumes. Do you have some time to add more checks to rename
as well?
-chris
next prev parent reply other threads:[~2009-11-12 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 5:30 Hard link across subvolumes TARUISI Hiroaki
2009-11-12 7:14 ` [PATCH] Deny sys_link " TARUISI Hiroaki
2009-11-12 15:00 ` Chris Mason [this message]
2009-11-13 6:17 ` TARUISI Hiroaki
2009-11-13 9:15 ` Yan, Zheng
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=20091112150039.GD3196@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=taruishi.hiroak@jp.fujitsu.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