public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: luto@mit.edu
Cc: kreijack@libero.it, linux-btrfs@vger.kernel.org
Subject: Re: BUG: Link from sub volume, then remove the subvolume -> wrong link
Date: Mon, 14 Dec 2009 08:42:44 +0900	[thread overview]
Message-ID: <4B257BF4.5060807@jp.fujitsu.com> (raw)
In-Reply-To: <4B23E378.1090905@mit.edu>

Hi,

We can see the patch in ML archive or at 'Patchwork' site.

  http://patchwork.kernel.org/patch/59519/

Thanks,
taruisi

(2009/12/13 3:39), Andy Lutomirski wrote:
> TARUISI Hiroaki wrote:
>> Hi,
>>
>>  I don't know how a hard link becomes to a soft link, hard link
>> across subvolumes should not allowed in btrfs.
>>
>>  Hard link contains target inode number but not target tree.
>> So, if we can create such hard link normally, it points to
>> a file which has same inode number in same subvolume.
>>  As for this problem, Christian Parpart posted a patch, and
>> I rebased it.
> 
> Can you post a link?  I'd like to test it, and it should probably go
> into -stable (since it fixes an oops that can be triggered without
> privileges).
> 
> Thanks,
> Andy


  reply	other threads:[~2009-12-13 23:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 19:54 BUG: Link from sub volume, then remove the subvolume -> wrong link Goffredo Baroncelli
2009-12-12  0:24 ` TARUISI Hiroaki
2009-12-12 13:54   ` Goffredo Baroncelli
2009-12-12 18:39   ` Andy Lutomirski
2009-12-13 23:42     ` TARUISI Hiroaki [this message]
2009-12-14 18:43       ` Andrew Lutomirski
2009-12-15  0:15         ` TARUISI Hiroaki
2009-12-15  4:04           ` Andy Lutomirski
2009-12-15 17:31             ` David Nicol
2009-12-17  0:00               ` TARUISI Hiroaki

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=4B257BF4.5060807@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=kreijack@libero.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=luto@mit.edu \
    /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