From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Cc: chris.mason@oracle.com
Subject: Hard link across subvolumes
Date: Fri, 30 Oct 2009 14:30:47 +0900 [thread overview]
Message-ID: <4AEA7A07.4020006@jp.fujitsu.com> (raw)
Hi,
In Btrfs, a hard link across subvolumes should be prohibited,
but not prohibited yet. (It may be convenient if possible,
I think.) If we make a hard link like this, filesystem may
abort or after umount/mount, contents of file may be swapped to
contents of other file(with same i-node number in same tree as
'from' file).
About this, I found Christian Parpart's patch posted last year,
and this patch seems to work well.
http://www.spinics.net/lists/linux-btrfs/msg00749.html
But this patch is not merged yet.
Some work(to check more, to change error code or to simply test)
shuould be done for this?
--
taruisi
next reply other threads:[~2009-10-30 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 5:30 TARUISI Hiroaki [this message]
2009-11-12 7:14 ` [PATCH] Deny sys_link across subvolumes TARUISI Hiroaki
2009-11-12 15:00 ` Chris Mason
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=4AEA7A07.4020006@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.