[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <673230ba-61d7-4c7f-aaf4-d5e2fc54944e@sapience.com>
Date: Thu, 7 Dec 2023 14:27:49 -0500
From: Genes Lists <lists@...ience.com>
To: Song Liu <song@...nel.org>
Cc: Guoqing Jiang <guoqing.jiang@...ux.dev>,
Bagas Sanjaya <bagasdotme@...il.com>, snitzer@...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>,
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
On 12/7/23 12:37, Song Liu wrote:
...
> kernel: md_end_clone_io+0x75/0xa0 <<< change in md_end_clone_io
>
> The commit only changes how we update bi_status. But bi_status was not
> used/checked at all between md_end_clone_io and the trap (lock cmpxchg).
> Did I miss something?
>
> Given the issue takes very long to reproduce. Maybe we have the issue
> before 6.6.4?
>
> Thanks,
> Song
Thanks for clarifying that point.
In meantime I rebooted server (shutdown was a struggle) - finally I
fsck'd the filesystem (ext4) sitting on the raid6 - and manually ran the
triggering rsync. This of course completed normally. That's either good
or bad depending on your perspective :)
If I can get it to crash again, I will either start a git bisect (from
6.6.3) or see if 6.7rc4 shows same issue.
thanks,
gene
Powered by blists - more mailing lists