From: "heming.zhao@suse.com" <heming.zhao@suse.com>
To: linux-raid@vger.kernel.org, song@kernel.org, guoqing.jiang@linux.dev
Cc: xni@redhat.com
Subject: Re: [PATCH v3] md/bitmap: don't set sb values if can't pass sanity check
Date: Wed, 30 Mar 2022 18:34:41 +0800 [thread overview]
Message-ID: <228810f7-90bf-15cf-37ba-c7977d35c046@suse.com> (raw)
In-Reply-To: <20220330102827.2593-1-heming.zhao@suse.com>
sorry for the mistake in v2 patch.
I had checked codes & tested module ko many times before sending v3.
- Heming
On 3/30/22 18:28, Heming Zhao wrote:
> If bitmap area contains invalid data, kernel will crash then mdadm
> triggers "Segmentation fault".
> This is cluster-md speical bug. In non-clustered env, mdadm will
> handle broken metadata case. In clustered array, only kernel space
> handles bitmap slot info. But even this bug only happened in clustered
> env, current sanity check is wrong, the code should be changed.
>
next prev parent reply other threads:[~2022-03-30 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:28 [PATCH v3] md/bitmap: don't set sb values if can't pass sanity check Heming Zhao
2022-03-30 10:34 ` heming.zhao [this message]
2022-03-31 7:06 ` Guoqing Jiang
2022-03-31 8:24 ` heming.zhao
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=228810f7-90bf-15cf-37ba-c7977d35c046@suse.com \
--to=heming.zhao@suse.com \
--cc=guoqing.jiang@linux.dev \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=xni@redhat.com \
/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