All of lore.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: chris.mason@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Deny sys_link across subvolumes.
Date: Fri, 13 Nov 2009 15:17:21 +0900	[thread overview]
Message-ID: <4AFCF9F1.9010502@jp.fujitsu.com> (raw)
In-Reply-To: <20091112150039.GD3196@think>

Chris Mason wrote:
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Thank you for your reply.

I tried moving file/directory/subvolume across subvolumes,
and found it worked. In source code of btrfs_rename, it's
already checked if 'from' directory and 'to' directory are
under a same root or not except a root object. If not
matched, btrfs_rename returns with -EXDEV but it seems mv
command treats it properly. Even if in no-check case (root
object case), I tried but found no serious problem.

I wonder renaming subvolumes across subvolumes does not
completely work yet in some points I cannot found, or
btrfs_rename works without returning -EXDEV.

Could you tell me how should we check when renaming
subvolumes?

Regards,
taruisi


  reply	other threads:[~2009-11-13  6:17 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
2009-11-13  6:17     ` TARUISI Hiroaki [this message]
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=4AFCF9F1.9010502@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.