linux-kernel - Re: md: regression: incorrect warn about updating super block failure

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] [day] [month] [year] [list]

Message-Id: <4eba52c0-a416-454b-a072-0965dfed722a@fnnas.com>
Date: Wed, 28 Jan 2026 17:30:18 +0800
From: "Yu Kuai" <yukuai@...as.com>
To: "Tj" <tj.iam.tj@...ton.me>
Cc: <linux-kernel@...r.kernel.org>, <linux-raid@...r.kernel.org>, 
	<yukuai@...as.com>
Subject: Re: md: regression: incorrect warn about updating super block failure

Hi,

在 2026/1/28 16:25, Tj 写道:
> Commit 8c9e376b9d1a222 introduces an error message that is incorrectly reported for LVM raid volumes:
>
> $ journalctl --dmesg --priority err
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
>   md_update_sb: can't update sb for read-only array mdX
Yeah, we should bypass dmraid, will fix it soon.
>
> $ sudo dmsetup table --target raid
> SUNNY-Documents: 0 20971520 raid raid1 3 0 region_size 4096 2 254:74 254:75 254:76 254:77
> SUNNY-Media: 0 171966464 raid raid1 3 0 region_size 4096 2 254:69 254:70 254:71 254:72
> SUNNY-NAS: 0 46874624 raid raid1 3 0 region_size 4096 2 254:15 254:16 254:17 254:18
> SUNNY-Projects: 0 23068672 raid raid1 3 0 region_size 4096 2 254:20 254:21 254:22 254:23
> SUNNY-SourceCode_wcorig: 0 478150656 raid raid1 3 0 region_size 4096 2 254:26 254:27 254:28 254:29
> SUNNY-WINE: 0 16777216 raid raid1 3 0 region_size 4096 2 254:80 254:81 254:82 254:83
> SUNNY-etc: 0 106496 raid raid1 3 0 region_size 4096 2 254:57 254:58 254:59 254:60
> SUNNY-home_wcorig: 0 301989888 raid raid1 3 0 region_size 4096 2 254:46 254:47 254:48 254:49
> SUNNY-l8r: 0 16777216 raid raid1 3 0 region_size 4096 2 254:37 254:38 254:39 254:40
> SUNNY-machines_old: 0 34185216 raid raid1 3 0 region_size 4096 2 254:32 254:33 254:34 254:35
> SUNNY-opt: 0 41943040 raid raid1 3 0 region_size 4096 2 254:64 254:65 254:66 254:67
> SUNNY-rootfs: 0 67108864 raid raid1 3 0 region_size 4096 2 254:3 254:4 254:5 254:6
> SUNNY-usr_local: 0 16777216 raid raid1 3 0 region_size 4096 2 254:52 254:53 254:54 254:55
> SUNNY-var_wcorig: 0 25165824 raid raid1 3 0 region_size 4096 2 254:9 254:10 254:11 254:12
>
>
-- 
Thansk,
Kuai