linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tavian Barnes <tavianator@tavianator.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org, wqu@suse.com
Subject: Re: [PATCH] btrfs: tree-checker: dump the page status if hit something wrong
Date: Tue, 13 Feb 2024 13:26:12 -0500	[thread overview]
Message-ID: <CABg4E-=AP9UXSzGh7a6Jw8FtC6RW6mNSuvaGpcL576buaCetOg@mail.gmail.com> (raw)
In-Reply-To: <CABg4E-kqfkX3nyVdcSsgucmcxdcJRMfH+ahVBR+bYXJyd0y53g@mail.gmail.com>

On Tue, Feb 13, 2024 at 1:07 PM Tavian Barnes <tavianator@tavianator.com> wrote:
> I tried to bisect but I don't know where to start from.  It still
> reproduces all the way back to v6.5, although with a different splat:

Oh I missed part of the splat:

      general protection fault, probably for non-canonical address
0x7f99872a6b80f0: 0000 [#1] PREEMPT SMP NOPTI
      BTRFS critical (device dm-3): corrupted node, root=518
block=16000637395156534217 owner mismatch, have 12049901028372027545
expect [256, 18446744073709551360]
      CPU: 47 PID: 3729 Comm: iou-wrk-3310 Not tainted 6.5.0-euclean
#10 4197dfd21e86f976fbd69cbd6a56016cf20d42e1
      Hardware name: Micro-Star International Co., Ltd. MS-7C60/TRX40
PRO WIFI (MS-7C60), BIOS 2.80 05/17/2022
>     RIP: 0010:btrfs_bin_search+0xd7/0x1d0 [btrfs]
>     ...

Normally I would suspect bad RAM for something like this, but I have
ECC memory and no reports of corrected errors.  0x7f99872a6b80f0
doesn't look like a single bit flip either.  I'm leaning towards it
being a race condition somewhere.

I'll run memtest anyway just to be sure.  I already ran btrfs check
with no errors.

-- 
Tavian Barnes

  reply	other threads:[~2024-02-13 18:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 23:48 [PATCH] btrfs: tree-checker: dump the page status if hit something wrong Qu Wenruo
2024-02-06  3:38 ` tavianator
2024-02-06  5:54   ` Qu Wenruo
2024-02-06 20:12     ` Tavian Barnes
2024-02-06 20:39       ` Qu Wenruo
2024-02-06 21:48         ` Tavian Barnes
2024-02-06 21:53           ` Qu Wenruo
2024-02-13 18:07             ` Tavian Barnes
2024-02-13 18:26               ` Tavian Barnes [this message]
2024-02-13 21:26               ` Qu Wenruo
2024-02-06 21:53           ` Tavian Barnes
2024-02-06 22:01             ` Qu Wenruo
2024-02-06 12:51   ` David Sterba
2024-02-06 20:19     ` Tavian Barnes
2024-02-06 12:46 ` David Sterba
2024-02-06 20:34   ` 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='CABg4E-=AP9UXSzGh7a6Jw8FtC6RW6mNSuvaGpcL576buaCetOg@mail.gmail.com' \
    --to=tavianator@tavianator.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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).