All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: receive: address setattr failures
Date: Thu,  3 Nov 2022 16:53:25 +0000	[thread overview]
Message-ID: <cover.1667494221.git.fdmanana@suse.com> (raw)

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

 cmds/receive.c       | 44 ++++++++++++++++++++++++++------------------
 common/send-stream.c |  2 +-
 2 files changed, 27 insertions(+), 19 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-11-03 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 16:53 fdmanana [this message]
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 ` [PATCH 0/2] btrfs-progs: receive: address setattr failures David Sterba

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=cover.1667494221.git.fdmanana@suse.com \
    --to=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 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.