Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>
Cc: linux-btrfs@vger.kernel.org, Igor Raits <igor@gooddata.com>,
	Jan Cipa <jan.cipa@gooddata.com>,
	Zdenek Pesek <zdenek.pesek@gooddata.com>,
	Daniel Secik <daniel.secik@gooddata.com>
Subject: Re: Linux 6.9.y btrfs: "NULL pointer dereference in attach_eb_folio_to_filemap" and "BUG: soft lockup" issues
Date: Mon, 17 Jun 2024 15:46:37 +0200	[thread overview]
Message-ID: <20240617134637.GG25756@twin.jikos.cz> (raw)
In-Reply-To: <CAK8fFZ5KVjrg0OO1eEXyC85Eg=97oP_CWvOdQ=1ZFKLKLOojyw@mail.gmail.com>

Hi,

On Mon, Jun 17, 2024 at 01:33:59PM +0200, Jaroslav Pulchart wrote:
> Hello,
> 
> We recently upgraded part of our production environment to kernel
> 6.9.y. Since then, we've been encountering random kernel "NULL pointer
> dereference" and "soft lockup" errors when using BTRFS. These issues
> occur sporadically, sometimes after several days, and I haven't been
> able to reproduce them consistently. Due to this unpredictability,
> bisecting is not a feasible option.
> 
> Attached are console logs from some instances of these issues:
> * "NULL pointer dereference" in "btrfs.issue.1.log"
> * "soft lockup" in "btrfs.issue.1.log"
> Any assistance with investigating and resolving these problems would
> be greatly appreciated.

thanks for the report, the symptoms match the problem that was fixed
recently by commit f3a5367c679d ("btrfs: protect folio::private when
attaching extent buffer folios").

> [1072053.328255] CPU: 15 PID: 2354438 Comm: kworker/u195:18 Tainted: G            E      6.9.3-1.gdc.el9.x86_64 #1

6.9.3 does not have the fix yet (unless you're using a manually patched
kernel), it's in 6.9.5.

  reply	other threads:[~2024-06-17 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 11:33 Linux 6.9.y btrfs: "NULL pointer dereference in attach_eb_folio_to_filemap" and "BUG: soft lockup" issues Jaroslav Pulchart
2024-06-17 13:46 ` David Sterba [this message]
2024-06-17 14:55   ` Jaroslav Pulchart
2024-07-01 11:39     ` Jaroslav Pulchart
2024-07-01 12:53       ` 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=20240617134637.GG25756@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=daniel.secik@gooddata.com \
    --cc=igor@gooddata.com \
    --cc=jan.cipa@gooddata.com \
    --cc=jaroslav.pulchart@gooddata.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zdenek.pesek@gooddata.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