From: Xiao Ni <xni@redhat.com>
To: jes@trained-monkey.org
Cc: ncroxon@redhat.com, ffan@redhat.com,
mariusz.tkaczyk@linux.intel.com, linux-raid@vger.kernel.org
Subject: [PATCH 1/1] mdadm/Detail: Can't show container name correctly when unpluging disks
Date: Wed, 20 Oct 2021 22:38:43 +0800 [thread overview]
Message-ID: <1634740723-5298-1-git-send-email-xni@redhat.com> (raw)
The test case is:
1. create one imsm container
2. create a raid5 device from the container
3. unplug two disks
4. mdadm --detail /dev/md126
[root@rhel85 ~]# mdadm -D /dev/md126
/dev/md126:
Container : ��, member 0
The Detail function first gets container name by function
map_dev_preferred. Then it tries to find which disks are
available. In patch db5377883fef(It should be FAILED..)
uses map_dev_preferred to find which disks are under /dev.
But now, the major/minor information comes from kernel space.
map_dev_preferred malloc memory and init a device list when
first be called by Detail. It can't find the device in the
list by the major/minor. It free the memory and reinit the
list.
The container name now points to an area tha has been freed.
So the containt is a mess.
This patch replaces map_dev_preferred with access.
Fixes: db5377883fef (It should be FAILED when raid has)
Signed-off-by: Xiao Ni <xni@redhat.com>
Reported-by: Fine Fan <ffan@redhat.com>
---
v2: use access rather than devid2kname
---
Detail.c | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/Detail.c b/Detail.c
index d3af0ab..df59378 100644
--- a/Detail.c
+++ b/Detail.c
@@ -351,14 +351,17 @@ int Detail(char *dev, struct context *c)
avail = xcalloc(array.raid_disks, 1);
for (d = 0; d < array.raid_disks; d++) {
- char *dv, *dv_rep;
- dv = map_dev_preferred(disks[d*2].major,
- disks[d*2].minor, 0, c->prefer);
- dv_rep = map_dev_preferred(disks[d*2+1].major,
- disks[d*2+1].minor, 0, c->prefer);
-
- if ((dv && (disks[d*2].state & (1<<MD_DISK_SYNC))) ||
- (dv_rep && (disks[d*2+1].state & (1<<MD_DISK_SYNC)))) {
+ char dv[32], dv_rep[32];
+
+ sprintf(dv, "/sys/dev/block/%d:%d",
+ disks[d*2].major, disks[d*2].minor);
+ sprintf(dv_rep, "/sys/dev/block/%d:%d",
+ disks[d*2+1].major, disks[d*2+1].minor);
+
+ if ((!access(dv, R_OK) &&
+ (disks[d*2].state & (1<<MD_DISK_SYNC))) ||
+ (!access(dv_rep, R_OK) &&
+ (disks[d*2+1].state & (1<<MD_DISK_SYNC)))) {
avail_disks ++;
avail[d] = 1;
} else
--
2.7.5
next reply other threads:[~2021-10-20 14:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 14:38 Xiao Ni [this message]
2021-10-21 9:13 ` [PATCH 1/1] mdadm/Detail: Can't show container name correctly when unpluging disks Tkaczyk, Mariusz
2021-10-22 0:09 ` Xiao Ni
2021-10-22 0:38 ` Xiao Ni
2021-11-02 16:00 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2021-10-15 9:25 Xiao Ni
2021-10-18 6:55 ` Tkaczyk, Mariusz
2021-10-18 7:15 ` Tkaczyk, Mariusz
2021-10-18 12:33 ` Xiao Ni
2021-10-18 9:58 ` Xiao Ni
2021-10-18 11:52 ` Tkaczyk, Mariusz
2021-10-18 13:05 ` Xiao Ni
2021-10-19 7:01 ` Jes Sorensen
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=1634740723-5298-1-git-send-email-xni@redhat.com \
--to=xni@redhat.com \
--cc=ffan@redhat.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=ncroxon@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;
as well as URLs for NNTP newsgroup(s).