From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Daniel Martinez <danielsmartinez@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: BUG: kernel NULL pointer dereference when using zstd
Date: Thu, 20 Aug 2020 07:31:15 +0800 [thread overview]
Message-ID: <4988ccc8-8c18-ecde-c6d4-bc2aa0360482@gmx.com> (raw)
In-Reply-To: <CAMmfObZhCNGDW6Z4jGHNA+ZCVP=tWvt=DLm1isuwRS4NEebp4Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]
On 2020/8/20 上午7:14, Daniel Martinez wrote:
> Hello,
>
> I have encountered a bug when using zstd compression (I assume that's
> what caused it, but I could be wrong) on the Debian kernel 5.7.10-1.
It's not zstd I guess, but a generic compression bug.
It's fixed by the upstream commit 1e6e238c3002 ("btrfs: inode: fix NULL
pointer dereference if inode doesn't need compression").
It's not yet merged into v5.7.y stable branch, I guess I need to
backport it manually then.
Thanks,
Qu
>
> Not sure if its relevant, but I may be hitting some corner case here,
> so my full storage stack is:
> Windows 10 -> VMware workstation full drive passthrough -> btrfs x2 -> mergerfs
>
> In btrfs, I have 2 arrays that are merged into one using mergerfs.
> (The use case here is to have different RAID profiles for different
> data in arbitrary locations):
> 3x8tb + 1x2tb in RAID1 meta+data - rw,noatime,space_cache=v2,autodefrag
> 1x2tb in Single data + DUP metadata -
> rw,noatime,space_cache,autodefrag,compress=zstd (this one is also
> using xxhash instead of CRC32)
>
> Syslog attached.
>
> Thanks,
> Daniel.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-19 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 23:14 BUG: kernel NULL pointer dereference when using zstd Daniel Martinez
2020-08-19 23:31 ` Qu Wenruo [this message]
2020-08-20 9:42 ` 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=4988ccc8-8c18-ecde-c6d4-bc2aa0360482@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=danielsmartinez@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox