[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPhsuW4n_=yL8PLj88x6ozFpUPmuayCiqCgtUYBQXrE70ivHbQ@mail.gmail.com>
Date: Tue, 6 Feb 2024 13:34:54 -0800
From: Song Liu <song@...nel.org>
To: Dan Moulding <dan@...m.net>
Cc: gregkh@...uxfoundation.org, junxiao.bi@...cle.com,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
regressions@...ts.linux.dev, stable@...r.kernel.org, yukuai1@...weicloud.com
Subject: Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system;
successfully bisected
On Tue, Feb 6, 2024 at 12:56 PM Dan Moulding <dan@...m.net> wrote:
>
> > Dan, could you please run the test on this branch
> > (83cbdaf61b1ab9cdaa0321eeea734bc70ca069c8)?
>
> I'm sorry to report that I can still reproduce the problem running the
> kernel built from the md-6.9 branch (83cbdaf61b1a).
>
> But the only commit I see on that branch that's not in master and
> touches raid5.c is this one:
>
> test@...rescue:~/src/linux$ git log master..song/md-6.9 drivers/md/raid5.c
> commit 61c90765e131e63ead773b9b99167415e246a945
> Author: Yu Kuai <yukuai3@...wei.com>
> Date: Thu Dec 28 20:55:51 2023 +0800
>
> md: remove redundant check of 'mddev->sync_thread'
>
> Is that expected, or were you expecting additional fixes to be in there?
I don't expect that commit to fix the issue. It is expected to be merged to
master in the next merge window. I am curious why I cannot reproduce
the issue. Let me try more..
Thanks,
Song
Powered by blists - more mailing lists