From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Forza <forza@tnonline.net>,
Linux btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Stable <stable@vger.kernel.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
a1bert@atlas.cz
Subject: Re: Fwd: vmalloc error: btrfs-delalloc btrfs_work_helper [btrfs] in kernel 6.3.x
Date: Tue, 23 May 2023 08:52:21 +0700 [thread overview]
Message-ID: <ZGwcVTpQNBoJHBB+@debian.me> (raw)
In-Reply-To: <fcf1d04.faed4a1a.18844d8e78f@tnonline.net>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
On Mon, May 22, 2023 at 09:04:05PM +0200, Forza wrote:
> I have a similar experience with kernel 6.3 where vmalloc fails in a similar way. I was able to reproduce it in a QEMU VM as well as on my system.
>
> https://lore.kernel.org/all/d11418b6-38e5-eb78-1537-c39245dc0b78@tnonline.net/T/
Thanks for your similar report. Telling regzbot about it:
#regzbot link: https://lore.kernel.org/all/d11418b6-38e5-eb78-1537-c39245dc0b78@tnonline.net/
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-23 1:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 13:25 Fwd: vmalloc error: btrfs-delalloc btrfs_work_helper [btrfs] in kernel 6.3.x Bagas Sanjaya
2023-05-22 16:00 ` Uladzislau Rezki
2023-05-22 19:09 ` David Sterba
2023-05-22 19:04 ` Forza
2023-05-23 1:52 ` Bagas Sanjaya [this message]
2023-05-23 10:28 ` Uladzislau Rezki
2023-05-23 21:25 ` Forza
2023-05-24 5:57 ` Forza
2023-05-24 9:13 ` David Sterba
2023-05-26 12:24 ` Uladzislau Rezki
2023-07-02 23:28 ` Forza
2023-07-06 8:08 ` Forza
2023-07-06 10:54 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-07 10:13 ` Forza
2023-08-02 11:41 ` default_enter_idle leaked IRQ state Forza
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=ZGwcVTpQNBoJHBB+@debian.me \
--to=bagasdotme@gmail.com \
--cc=a1bert@atlas.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=forza@tnonline.net \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).