From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs-progs: receive: address setattr failures
Date: Fri, 11 Nov 2022 16:36:17 +0100 [thread overview]
Message-ID: <20221111153617.GP5824@twin.jikos.cz> (raw)
In-Reply-To: <cover.1667494221.git.fdmanana@suse.com>
On Thu, Nov 03, 2022 at 04:53:25PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> I was writing a test case for fstests with fsstress and send v2 streams
> and it turns out that receive will always fail if we have a fileattr
> command in the stream. It fails for two different reasons, described in
> the changelog.
>
> We actually had a report today of a receiver failing on a send stream v2
> because of the reason addressed in the first patch. However fixing that
> alone, will still cause the receiver to fail, just for a different reason
> (patch 2).
>
> For now I'll hold the test case for fstests since it fails very frequently
> (almost always actually).
>
> Filipe Manana (2):
> btrfs-progs: receive: fix parsing of attributes field from the fileattr command
> btrfs-progs: receive: work around failure of fileattr commands
Added to devel, thanks.
prev parent reply other threads:[~2022-11-11 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 16:53 [PATCH 0/2] btrfs-progs: receive: address setattr failures fdmanana
2022-11-03 16:53 ` [PATCH 1/2] btrfs-progs: receive: fix parsing of attributes field from the fileattr command fdmanana
2022-11-03 16:53 ` [PATCH 2/2] btrfs-progs: receive: work around failure of fileattr commands fdmanana
2022-11-11 15:36 ` David Sterba [this message]
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=20221111153617.GP5824@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--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