From: Su Yue <l@damenly.su>
To: dsterba@suse.cz
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 5.15.0-rc1 armv7hl Workqueue: btrfs-delalloc btrfs_work_helper PC is at mmiocpy LR is at ZSTD_compressStream
Date: Mon, 04 Oct 2021 19:57:25 +0800 [thread overview]
Message-ID: <v92d3sjs.fsf@damenly.su> (raw)
In-Reply-To: <20210921195632.GR9286@twin.jikos.cz>
On Tue 21 Sep 2021 at 21:56, David Sterba <dsterba@suse.cz> wrote:
> On Mon, Sep 20, 2021 at 06:13:07PM -0600, Chris Murphy wrote:
>> https://kojipkgs.fedoraproject.org//work/tasks/8820/75928820/oz-armhfp.log
>
>> 00:09:50,679 EMERG kernel:[<c08bd768>] (mmiocpy) from
>> [<c089c314>]
>> (ZSTD_compressStream+0x184/0x294)
>
> The last function to fail is inside ZSTD implementation in
> kernel.
> If btrfs passes wrong data to zstd we'd see that also on non-arm
> builds,
> so guessing by mmiocpy as a copy-something function it could be
> some
> sort of alignment problem that works on x86_64 but throws an
> exception
> on arm as it's stricter about alignment.
It's about 32bits platforms. There is another report about x86
cpu.
And it's reproduciable by running btrfs/004 (lzo and zstd)in x86
VM.
In my arm64, all things are fine.
And the bisection result is the highmem related patchset
'[PATCH 0/6] Remove highmem allocations, kmap/kunmap'.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=214565
--
Su
next prev parent reply other threads:[~2021-10-04 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 0:13 5.15.0-rc1 armv7hl Workqueue: btrfs-delalloc btrfs_work_helper PC is at mmiocpy LR is at ZSTD_compressStream Chris Murphy
2021-09-21 14:11 ` Chris Murphy
2021-09-21 19:56 ` David Sterba
2021-10-04 11:57 ` Su Yue [this message]
2021-10-04 12:19 ` 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=v92d3sjs.fsf@damenly.su \
--to=l@damenly.su \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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.