public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
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 v2] md/bitmap: don't set sb values if can't pass sanity check
Date: Tue, 29 Mar 2022 15:33:41 +0800	[thread overview]
Message-ID: <471a3df2-9fac-59a0-7bec-1fcd1d1c5de5@suse.com> (raw)
In-Reply-To: <20220329072722.1786-1-heming.zhao@suse.com>

On 3/29/22 15:27, 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> ... ...
> 
> Signed-off-by: Heming Zhao <heming.zhao@suse.com>
> ---
> v2: * revise commit log
>        - change mdadm "FPE" error to "Segmentation fault" error
>          ("FPE" belongs to another issue)
>        - add kernel crash log
>      * modify a comment style to follow code rule
>      * change strlcpy to strscpy for strlcpy is marked as deprecated in
>        Documentation/process/deprecated.rst
>        - note: strlcpy() still exists in md.c & md-cluster.c

Please note, beside Guoqing's review comments, I added new code change : strlcpy() => strscpy()

- Heming



      reply	other threads:[~2022-03-29  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  7:27 [PATCH v2] md/bitmap: don't set sb values if can't pass sanity check Heming Zhao
2022-03-29  7:33 ` heming.zhao [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=471a3df2-9fac-59a0-7bec-1fcd1d1c5de5@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