Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: non-atomic xattr replacement in btrfs => rsync random errors
Date: Fri, 7 Nov 2014 09:29:16 +0000 (UTC)	[thread overview]
Message-ID: <pan.2014.11.07.09.29.16@googlemail.com> (raw)
In-Reply-To: orfvdvaix5.fsf@free.home

On Thu, 06 Nov 2014 23:39:02 -0200, Alexandre Oliva wrote:

> [dropping rsync@lists.samba.org, it rejects posts from non-subscribers;
>  refer to https://bugzilla.samba.org/show_bug.cgi?id=10925 instead]
> 
> On Nov  6, 2014, Alexandre Oliva <oliva@gnu.org> wrote:
> 
>> What makes the problem visible is that btrfs appears to have a race in
>> its handling of xattr replacement, leaving a window between the removal
>> of the old value and the insertion of the new one
> 
> The bugs described above occurred with rsync-3.1.0-5.fc20.x86_64 and
> kernel-libre-3.16.7-200.fc20.gnu.x86_64.  The btrfs code in kernel-libre
> is unchanged from the corresponding Fedora kernel.  The distro is BLAG
> 200k/x86_64, under development.

Just a shot in the dark - could this be related to commit:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b0d5d10f41a0f1cd839408dd94427f2db3553bca

I don't think that made it into 3.16.x.

-h


  reply	other threads:[~2014-11-07  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  0:37 non-atomic xattr replacement in btrfs => rsync random errors Alexandre Oliva
2014-11-07  1:39 ` Alexandre Oliva
2014-11-07  9:29   ` Holger Hoffstätte [this message]
2014-11-07 11:21 ` Filipe David Manana

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=pan.2014.11.07.09.29.16@googlemail.com \
    --to=holger.hoffstaette@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox