From: "Tanska, Kinga" <kinga.tanska@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Kinga Tanska <kinga.tanska@intel.com>,
linux-raid@vger.kernel.org, jes@trained-monkey.org,
colyli@suse.de
Subject: Re: [PATCH] Mdmonitor: Fix segfault and improve logging
Date: Mon, 4 Apr 2022 14:39:54 +0200 [thread overview]
Message-ID: <321885a5-f9c8-f9c2-fab2-2c31ead17b87@linux.intel.com> (raw)
In-Reply-To: <9eccf3ed-3db3-7ba7-fd8b-fa4273bc0752@molgen.mpg.de>
Hello Paul,
I've tried to reproduce it with mdadm 4.1 and mdadm 4.2 and both apps
exit with
segmentation fault. This patch is not a fix, it adds checking if device
is md array.
It hasn't been checked before in mdmonitor, so segmentation fault should
appear.
Regards,
Kinga
On 3/23/2022 11:31 AM, Paul Menzel wrote:
Dear Kinga,
Am 23.03.22 um 10:02 schrieb Tanska, Kinga:
> I will send splitted patches in next messages.
Thank you.
> There are steps to reproduce:
>
> 1. Stop mdmonitor instance e.g.
>
> # systemctl stop mdmonitor
>
> 2. Run mdmonitor for non-md device e.g.
>
> # mdadm --monitor /dev/nvme1n1
>
>
> Call trace:
>
> #0 0x00007ffff7617518 in __strcpy_sse2_unaligned () from
> /usr/lib64/libc.so.6
> #1 0x000000000042bc9e in check_array ()
> #2 0x000000000042c7af in Monitor ()
> #3 0x0000000000406edc in main ()
I am unable to reproduce it with mdadm 4.1:
$ sudo strace mdadm --monitor /dev/sda
execve("/usr/bin/mdadm", ["mdadm", "--monitor", "/dev/sda"],
0x7ffc8b00e880 /* 14 vars */) = 0
[…]
openat(AT_FDCWD, "/dev/sda", O_RDONLY) = 3
fstat(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0), ...}) = 0
readlink("/sys/dev/block/8:0", "../../devices/pci0000:00/0000:00"...,
199) = 91
close(3) = 0
pselect6(1, NULL, NULL, [], {tv_sec=1000, tv_nsec=0}, NULL) = ?
ERESTARTNOHAND (To be restarted if no handler)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
pselect6(1, NULL, NULL, [], {tv_sec=999, tv_nsec=568020697}, NULL)
= ? ERESTARTNOHAND (To be restarted if no handler)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
pselect6(1, NULL, NULL, [], {tv_sec=999, tv_nsec=521836826}, NULL
Did a specific commit introduce the problem? If so, it’d be great if you
added a Fixes line.
[…]
Kind regards,
Paul
next prev parent reply other threads:[~2022-04-04 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 12:32 [PATCH] Mdmonitor: Fix segfault and improve logging Kinga Tanska
2022-03-21 12:45 ` Paul Menzel
2022-03-23 9:02 ` Tanska, Kinga
2022-03-23 10:31 ` Paul Menzel
2022-04-04 12:39 ` Tanska, Kinga [this message]
2022-04-04 12:54 ` Paul Menzel
-- strict thread matches above, loose matches on Subject: below --
2022-01-20 12:32 Kinga Tanska
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=321885a5-f9c8-f9c2-fab2-2c31ead17b87@linux.intel.com \
--to=kinga.tanska@linux.intel.com \
--cc=colyli@suse.de \
--cc=jes@trained-monkey.org \
--cc=kinga.tanska@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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