From: Qu Wenruo <wqu@suse.com>
To: u-boot@lists.denx.de
Cc: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] uboot: fs/btrfs: Fix read error on LZO compressed extents
Date: Thu, 19 Mar 2020 20:30:04 +0800 [thread overview]
Message-ID: <20200319123006.37578-1-wqu@suse.com> (raw)
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(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Qu Wenruo <wqu@suse.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] uboot: fs/btrfs: Fix read error on LZO compressed extents
Date: Thu, 19 Mar 2020 20:30:04 +0800 [thread overview]
Message-ID: <20200319123006.37578-1-wqu@suse.com> (raw)
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(-)
--
2.25.1
next reply other threads:[~2020-03-19 12:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 12:30 Qu Wenruo [this message]
2020-03-19 12:30 ` [PATCH 0/2] uboot: fs/btrfs: Fix read error on LZO compressed extents Qu Wenruo
2020-03-19 12:30 ` [PATCH 1/2] uboot: fs/btrfs: Use LZO_LEN to replace immediate number Qu Wenruo
2020-03-19 12:30 ` Qu Wenruo
2020-03-19 12:30 ` [PATCH 2/2] uboot: fs/btrfs: Fix LZO false decompression error caused by pending zero Qu Wenruo
2020-03-19 12:30 ` Qu Wenruo
2020-03-19 13:33 ` Matthias Brugger
2020-03-19 13:33 ` Matthias Brugger
2020-03-19 13:56 ` David Sterba
2020-03-19 13:56 ` David Sterba
2020-03-19 14:34 ` Matthias Brugger
2020-03-19 14:34 ` Matthias Brugger
2020-03-19 16:28 ` David Sterba
2020-03-19 16:28 ` David Sterba
2020-03-24 11:03 ` Qu Wenruo
2020-03-24 11:03 ` Qu Wenruo
2020-03-25 7:58 ` Marek Behun
2020-03-25 7:58 ` Marek Behun
2020-03-24 11:03 ` Qu Wenruo
2020-03-24 11:03 ` Qu Wenruo
2020-03-19 12:33 [PATCH 0/2] uboot: fs/btrfs: Fix read error on LZO compressed extents Qu Wenruo
2020-03-19 12:33 ` Qu Wenruo
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=20200319123006.37578-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=u-boot@lists.denx.de \
/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.