[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALTww28Fz5Y11q1UE8r6qRrwOHgKOWw=iX3AisoSFGh_VhAbJA@mail.gmail.com>
Date: Fri, 8 Dec 2023 00:15:38 +0800
From: Xiao Ni <xni@...hat.com>
To: Genes Lists <lists@...ience.com>
Cc: snitzer@...nel.org, song@...nel.org, yukuai3@...wei.com,
axboe@...nel.dk, mpatocka@...hat.com, heinzm@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: md raid6 oops in 6.6.4 stable
On Thu, Dec 7, 2023 at 9:12 PM Genes Lists <lists@...ience.com> wrote:
>
> I have not had chance to git bisect this but since it happened in stable
> I thought it was important to share sooner than later.
>
> One possibly relevant commit between 6.6.3 and 6.6.4 could be:
>
> commit 2c975b0b8b11f1ffb1ed538609e2c89d8abf800e
> Author: Song Liu <song@...nel.org>
> Date: Fri Nov 17 15:56:30 2023 -0800
>
> md: fix bi_status reporting in md_end_clone_io
>
> log attached shows page_fault_oops.
> Machine was up for 3 days before crash happened.
>
> gene
Hi all
I'm following the crash reference rule to try to find some hints. The
RDI is ffff8881019312c0 which should be the address of struct
block_device *part. And the CR2 is ffff8881019312e8. So the panic
happens when it wants to introduce part->bd_stamp. Hope it's helpful
if the addresses are right.
Best Regards
Xiao
Powered by blists - more mailing lists