From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Su Yue <l@damenly.su>, Chris Murphy <lists@colorremedies.com>
Cc: Nikolay Borisov <nborisov@suse.com>, Qu Wenruo <wqu@suse.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 5.14.9 aarch64 OOPS Workqueue: btrfs-delalloc btrfs_work_helper
Date: Mon, 18 Oct 2021 21:28:47 +0800 [thread overview]
Message-ID: <e75cf666-0b3a-9819-c6ac-a34835734bfb@gmx.com> (raw)
In-Reply-To: <bl3mimya.fsf@damenly.su>
On 2021/10/18 19:32, Su Yue wrote:
>
> On Sun 17 Oct 2021 at 21:57, Chris Murphy <lists@colorremedies.com> wrote:
>
>> Any update on this problem and whether+what more info is needed?
>>
> It's interesting the OOPS only happens in openstack environment.
Or the toolchain?
I also tried my misc-next build using GCC on my RPI4, fstests with
compression never crashes the kernel.
Thanks,
Qu
> Is it possiable to provide the kernel core dump?
>
> --
> Su
>> Thanks,
>> Chris Murphy
>>
>> On Wed, Oct 13, 2021 at 3:21 PM Chris Murphy <lists@colorremedies.com>
>> wrote:
>>>
>>> From the downstream bug:
>>>
>>> [root@openqa-a64-worker03 adamwill][PROD]#
>>> /usr/src/kernels/5.14.9-300.fc35.aarch64/scripts/faddr2line
>>> /usr/lib/debug/lib/modules/5.14.9-300.fc35.aarch64/vmlinux
>>> submit_compressed_extents+0x38
>>> submit_compressed_extents+0x38/0x3d0:
>>> submit_compressed_extents at
>>> /usr/src/debug/kernel-5.14.9/linux-5.14.9-300.fc35.aarch64/fs/btrfs/inode.c:845
>>>
>>> [root@openqa-a64-worker03 adamwill][PROD]#
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=2011928#c26
>>>
>>> Also curious: this problem is only happening in openstack
>>> environments, as if the host environment matters. Does that make
>>> sense?
>>>
>>>
>>> --
>>> Chris Murphy
next prev parent reply other threads:[~2021-10-18 13:30 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 0:59 5.14.9 aarch64 OOPS Workqueue: btrfs-delalloc btrfs_work_helper Chris Murphy
2021-10-12 5:25 ` Nikolay Borisov
2021-10-12 6:47 ` Qu Wenruo
2021-10-12 14:30 ` Chris Murphy
2021-10-12 21:24 ` Chris Murphy
2021-10-12 23:55 ` Qu Wenruo
2021-10-13 12:14 ` Chris Murphy
2021-10-13 12:18 ` Qu Wenruo
2021-10-13 12:27 ` Chris Murphy
2021-10-13 12:29 ` Nikolay Borisov
2021-10-13 12:43 ` Chris Murphy
2021-10-13 12:46 ` Nikolay Borisov
2021-10-13 12:55 ` Chris Murphy
2021-10-13 19:21 ` Chris Murphy
2021-10-18 1:57 ` Chris Murphy
2021-10-18 11:32 ` Su Yue
2021-10-18 13:28 ` Qu Wenruo [this message]
2021-10-18 14:49 ` Chris Murphy
2021-10-18 18:24 ` Chris Murphy
2021-10-19 1:24 ` Su Yue
2021-10-19 18:26 ` Chris Murphy
2021-10-19 23:42 ` Su Yue
2021-10-20 1:21 ` Qu Wenruo
2021-10-20 1:25 ` Chris Murphy
2021-10-20 23:55 ` Chris Murphy
2021-10-21 0:29 ` Su Yue
2021-10-21 0:37 ` Qu Wenruo
2021-10-21 0:46 ` Su Yue
2021-10-21 14:43 ` Chris Murphy
2021-10-21 14:48 ` Chris Murphy
2021-10-21 14:51 ` Nikolay Borisov
2021-10-21 14:55 ` Chris Murphy
2021-10-21 15:01 ` Nikolay Borisov
2021-10-21 15:06 ` Chris Murphy
2021-10-21 15:32 ` Chris Murphy
2021-10-21 18:07 ` Chris Murphy
2021-10-21 5:56 ` Nikolay Borisov
2021-10-22 2:36 ` Chris Murphy
2021-10-22 6:02 ` Nikolay Borisov
2021-10-22 6:17 ` Su Yue
2021-10-22 10:44 ` Nikolay Borisov
2021-10-22 11:43 ` Nikolay Borisov
2021-10-22 17:18 ` Chris Murphy
2021-10-23 10:09 ` Nikolay Borisov
2021-10-25 14:48 ` Chris Murphy
2021-10-25 18:34 ` Chris Murphy
2021-10-25 19:40 ` Chris Murphy
2021-10-26 7:14 ` Nikolay Borisov
2021-10-26 12:51 ` Chris Murphy
2021-10-26 13:05 ` Nikolay Borisov
2021-10-26 18:08 ` Chris Murphy
2021-10-26 18:14 ` Nikolay Borisov
2021-10-26 18:26 ` Chris Murphy
2021-10-26 18:31 ` Chris Murphy
2021-10-26 18:35 ` Nikolay Borisov
2021-10-27 18:22 ` Chris Murphy
2021-10-28 5:36 ` Nikolay Borisov
2021-11-02 14:23 ` Chris Murphy
2021-11-02 14:25 ` Nikolay Borisov
2021-11-05 16:12 ` Chris Murphy
2021-11-07 9:11 ` Nikolay Borisov
2021-10-19 1:25 ` 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=e75cf666-0b3a-9819-c6ac-a34835734bfb@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=l@damenly.su \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=nborisov@suse.com \
--cc=wqu@suse.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 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).