[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <714b22c7-b8dd-008d-a1ea-a184dc8ec1cf@linux.dev>
Date: Thu, 7 Dec 2023 22:42:44 +0800
From: Guoqing Jiang <guoqing.jiang@...ux.dev>
To: Genes Lists <lists@...ience.com>,
Bagas Sanjaya <bagasdotme@...il.com>, snitzer@...nel.org,
song@...nel.org, yukuai3@...wei.com, axboe@...nel.dk,
mpatocka@...hat.com, heinzm@...hat.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux RAID <linux-raid@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>
Cc: Bhanu Victor DiCara <00bvd0+linux@...il.com>,
Xiao Ni <xni@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: md raid6 oops in 6.6.4 stable
Hi,
On 12/7/23 21:55, Genes Lists wrote:
> On 12/7/23 08:30, Bagas Sanjaya wrote:
>> On Thu, Dec 07, 2023 at 08:10:04AM -0500, Genes Lists 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.
Could you decode the oops (I can't find it in lore for some reason)
([1])? And
can it be reproduced reliably? If so, pls share the reproduce step.
[1]. https://lwn.net/Articles/592724/
Thanks,
Guoqing
Powered by blists - more mailing lists