mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Corey Hickey <bugfood-c@fatooh.org>
To: incharilla@incharilla.site, Song Liu <song@kernel.org>,
	Yu Kuai <yukuai@fygo.io>, Li Nan <magiclinan@didiglobal.com>,
	Xiao Ni <xiao@kernel.org>
Cc: Yu Kuai <yukuai@fnnas.com>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md: dont warn about sb update on auto read only arrays
Date: Sat, 7 Nov 2026 15:50:15 -0800	[thread overview]
Message-ID: <b1065a1a-1559-4719-bd2f-7967b84be587@fatooh.org> (raw)
In-Reply-To: <20261106-md-auto-read-only-sb-warn-v1-1-5bfde3559841@incharilla.site>

On 2026-11-06 10:20, incharilla via B4 Relay wrote:
> Skip the message for MD_AUTO_READ the same way dm raid is already skipped.
> It is still printed for arrays that are really read only.

Thank you. I tested this on Linus's tree and checked messages upon bootup.


With a41e364995bbcfa627418a70fe913c35b7510728 (unpatched):

$ sudo dmesg | grep 'read-only array'
[    1.589087] md_update_sb: can't update sb for read-only array md2
[    1.758035] md_update_sb: can't update sb for read-only array md1
[    1.773313] md_update_sb: can't update sb for read-only array md0
[    1.885346] md_update_sb: can't update sb for read-only array md3


With your patch on top:

$ sudo dmesg | grep 'read-only array'

(no messages)


I also was no longer able to reproduce the message when creating a 
degraded RAID-1 array.

This seems good to me.

Tested-by: Corey Hickey <bugfood-c@fatooh.org>

Thanks,
Corey

      reply	other threads:[~2026-11-07 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 18:20 incharilla via B4 Relay
2026-11-07 23:50 ` Corey Hickey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b1065a1a-1559-4719-bd2f-7967b84be587@fatooh.org \
    --to=bugfood-c@fatooh.org \
    --cc=incharilla@incharilla.site \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=magiclinan@didiglobal.com \
    --cc=song@kernel.org \
    --cc=xiao@kernel.org \
    --cc=yukuai@fnnas.com \
    --cc=yukuai@fygo.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®