stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH] Btrfs: incremental send, fix file corruption when no-holes feature is enabled
       [not found] <20190520085542.29282-1-fdmanana@kernel.org>
@ 2019-05-20 13:58 ` Sasha Levin
  0 siblings, 0 replies; only message in thread
From: Sasha Levin @ 2019-05-20 13:58 UTC (permalink / raw)
  To: Sasha Levin, Filipe Manana, linux-btrfs; +Cc: stable

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-05-20 13:58 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20190520085542.29282-1-fdmanana@kernel.org>
2019-05-20 13:58 ` [PATCH] Btrfs: incremental send, fix file corruption when no-holes feature is enabled Sasha Levin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).