From patchwork Thu Mar 19 12:33:17 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Qu Wenruo X-Patchwork-Id: 243929 List-Id: U-Boot discussion From: wqu at suse.com (Qu Wenruo) Date: Thu, 19 Mar 2020 20:33:17 +0800 Subject: [PATCH 0/2] uboot: fs/btrfs: Fix read error on LZO compressed extents Message-ID: <20200319123319.37848-1-wqu@suse.com> There is a bug that uboot can't load LZO compressed data extent while kernel can handle it without any problem. It turns out to be a page boundary case. The 2nd patch is the proper fix, backported from btrfs-progs. The first patch is just to make my eyes less hurt. I guess it's time to backport proper code from btrfs-progs, other than using tons of immediate numbers. Qu Wenruo (2): uboot: fs/btrfs: Use LZO_LEN to replace immediate number uboot: fs/btrfs: Fix LZO false decompression error caused by pending zero fs/btrfs/compression.c | 42 ++++++++++++++++++++++++++++++++---------- 1 file changed, 32 insertions(+), 10 deletions(-)