From: Martin Wilck <mwilck@suse.com>
To: lixiaokeng <lixiaokeng@huawei.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: dm-devel@redhat.com
Subject: Re: [dm-devel] [PATCH] multipathd: avoid crash in uevent_cleanup()
Date: Thu, 04 Feb 2021 16:06:36 +0100 [thread overview]
Message-ID: <57ec651871345e3aae745ba3a75c5f1e59bc25ef.camel@suse.com> (raw)
In-Reply-To: <45fe03c8-1cc0-4318-ae84-698959667a6b@huawei.com>
On Thu, 2021-02-04 at 09:40 +0800, lixiaokeng wrote:
>
>
> On 2021/2/3 21:57, Martin Wilck wrote:
> > > If exit() before all pthread_cancel in child of 0.7.7, there is
> > > no
> > > any crash.
> > What do you mean with "exit() before all pthread_cancel"? If this
> > happens on pthread_cancel(), and you don't call that function, this
> > would actually be expected.
>
> When running_state is DAEMON_SHUTDOWN, break while then _exit(0). But
> is is not a great method.
I wonder if it would be possible to figure out the LWP numbers (process
IDs) of the different threads before the crash occurs, and compare this
to the gdb output
(gdb) info threads
Id Target Id Frame
* 1 LWP 1997690 0x00007f59a0109647 in ?? ()
2 LWP 1996840 0x00007f59a0531de7 in ?? ()
3 LWP 1997692 0x00007f59a0109647 in ?? ()
4 LWP 1996857 0x00007f59a020d169 in ?? ()
... to identify which thread crashed, and if it's always the same one.
Martin
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-02-04 15:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 21:08 [dm-devel] [PATCH] multipathd: avoid crash in uevent_cleanup() mwilck
2021-02-02 20:52 ` Martin Wilck
2021-02-03 10:48 ` lixiaokeng
2021-02-03 13:57 ` Martin Wilck
2021-02-04 1:40 ` lixiaokeng
2021-02-04 15:06 ` Martin Wilck [this message]
2021-02-05 11:08 ` Martin Wilck
2021-02-05 11:09 ` Martin Wilck
2021-02-07 7:05 ` lixiaokeng
2021-03-01 14:53 ` lixiaokeng
2021-03-02 8:41 ` lixiaokeng
2021-03-02 11:07 ` Martin Wilck
2021-03-02 15:49 ` lixiaokeng
2021-03-02 9:56 ` Martin Wilck
2021-03-02 12:44 ` lixiaokeng
2021-03-02 15:29 ` Martin Wilck
2021-03-02 16:55 ` Martin Wilck
2021-03-03 10:42 ` lixiaokeng
2021-03-08 9:40 ` Martin Wilck
2021-03-15 13:00 ` Martin Wilck
2021-03-16 11:12 ` lixiaokeng
2021-03-17 16:59 ` Martin Wilck
2021-03-19 1:49 ` lixiaokeng
2021-02-08 7:41 ` lixiaokeng
2021-02-08 9:50 ` Martin Wilck
2021-02-08 10:49 ` lixiaokeng
2021-02-08 11:03 ` Martin Wilck
2021-02-09 1:36 ` lixiaokeng
2021-02-09 17:30 ` Martin Wilck
2021-02-10 2:02 ` lixiaokeng
2021-02-10 2:29 ` Hexiaowen (Hex, EulerOS)
2021-02-19 10:35 ` Martin Wilck
2021-02-19 1:36 ` lixiaokeng
2021-02-02 22:23 ` Benjamin Marzinski
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=57ec651871345e3aae745ba3a75c5f1e59bc25ef.camel@suse.com \
--to=mwilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=lixiaokeng@huawei.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).