linux-kernel - Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system; successfully bisected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2b5daa31-af66-4297-932b-d2fd341b63e6@linux.intel.com>
Date: Wed, 21 Feb 2024 15:50:26 +0100
From: Mateusz Kusiak <mateusz.kusiak@...ux.intel.com>
To: junxiao.bi@...cle.com, Dan Moulding <dan@...m.net>
Cc: gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
 linux-raid@...r.kernel.org, regressions@...ts.linux.dev, song@...nel.org,
 stable@...r.kernel.org
Subject: Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system;
 successfully bisected

On 21.02.2024 00:15, junxiao.bi@...cle.com wrote:
>
> The thing is we can't reproduce this issue at all. If you can generate 
> a vmcore when the hung happened, then we can review which processes 
> are stuck.
>
Hi,
don't know if that be any of help, but I run below scenario with SATA 
and NVMe drives. For me, the issue is reproducible on NVMe drives only.

Scenario:
1. Create R5D3 with native metadata
     # mdadm -CR /dev/md/vol -l5 -n3 /dev/nvme[0-2]n1 --assume-clean
2. Create FS on the array
     # mkfs.ext4 /dev/md/vol -F
3. Remove single member drive via "--incremental --fail"
     # mdadm -If nvme0n1

The result is almost instant.

Thanks,
Mateusz