All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 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: Fwd: vmalloc error: btrfs-delalloc btrfs_work_helper [btrfs] in kernel 6.3.x
Date: Mon, 22 May 2023 20:25:42 +0700	[thread overview]
Message-ID: <efa04d56-cd7f-6620-bca7-1df89f49bf4b@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> after updating from 6.2.x to 6.3.x, vmalloc error messages started to appear in the dmesg
> 
> 
> 
> # free 
>                total        used        free      shared  buff/cache   available
> Mem:        16183724     1473068      205664       33472    14504992    14335700
> Swap:       16777212      703596    16073616
> 
> 
> (zswap enabled)

See bugzilla for the full thread and attached dmesg.

On the report, the reporter can't perform the required bisection,
unfortunately.

Anyway, I'm adding it to regzbot:

#regzbot introduced: v6.2..v6.3 https://bugzilla.kernel.org/show_bug.cgi?id=217466
#regzbot title: btrfs_work_helper dealloc error in v6.3.x

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217466

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-05-22 13:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 13:25 Bagas Sanjaya [this message]
2023-05-22 16:00 ` Fwd: vmalloc error: btrfs-delalloc btrfs_work_helper [btrfs] in kernel 6.3.x Uladzislau Rezki
2023-05-22 19:09   ` David Sterba
2023-05-22 19:04 ` Forza
2023-05-23  1:52   ` Bagas Sanjaya
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=efa04d56-cd7f-6620-bca7-1df89f49bf4b@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=a1bert@atlas.cz \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --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 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.