From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Filipe Manana <fdmanana@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] Btrfs: incremental send, fix file corruption when no-holes feature is enabled
Date: Mon, 20 May 2019 13:58:12 +0000 [thread overview]
Message-ID: <20190520135813.4D7E9216FD@mail.kernel.org> (raw)
In-Reply-To: <20190520085542.29282-1-fdmanana@kernel.org>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 16e7549f045d Btrfs: incompatible format change to remove hole extents.
The bot has tested the following trees: v5.1.3, v5.0.17, v4.19.44, v4.14.120, v4.9.177, v4.4.180, v3.18.140.
v5.1.3: Build OK!
v5.0.17: Build OK!
v4.19.44: Build OK!
v4.14.120: Failed to apply! Possible dependencies:
22d3151c2c4c ("Btrfs: send, fix incorrect file layout after hole punching beyond eof")
v4.9.177: Failed to apply! Possible dependencies:
22d3151c2c4c ("Btrfs: send, fix incorrect file layout after hole punching beyond eof")
v4.4.180: Failed to apply! Possible dependencies:
22d3151c2c4c ("Btrfs: send, fix incorrect file layout after hole punching beyond eof")
v3.18.140: Failed to apply! Possible dependencies:
22d3151c2c4c ("Btrfs: send, fix incorrect file layout after hole punching beyond eof")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-05-20 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 8:55 [PATCH] Btrfs: incremental send, fix file corruption when no-holes feature is enabled fdmanana
2019-05-20 13:58 ` Sasha Levin [this message]
2019-05-27 15:21 ` 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=20190520135813.4D7E9216FD@mail.kernel.org \
--to=sashal@kernel.org \
--cc=stable@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.