From: Alexander Aring <aahringo@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCHv2 dlm-tool 1/2] dlm_controld: be sure we close logging at last
Date: Wed, 5 Oct 2022 15:23:11 -0400 [thread overview]
Message-ID: <20221005192312.4130838-1-aahringo@redhat.com> (raw)
I currently try to debug the following:
(gdb) bt
0 _int_malloc (av=av at entry=0x7fd353ac2bc0 <main_arena>, bytes=bytes at entry=8192) at malloc.c:3755
1 0x00007fd3537a04a6 in __libc_calloc (n=n at entry=1, elem_size=elem_size at entry=8192) at malloc.c:3445
2 0x00007fd353792bd7 in __GI___open_memstream (bufloc=bufloc at entry=0x7ffc4edd2ea0, sizeloc=sizeloc at entry=0x7ffc4edd2ea8) at memstream.c:83
3 0x00007fd35382cba4 in __GI___vsyslog_chk (pri=163, flag=1, fmt=0x5560190522da "%s", ap=0x7ffc4edd2f90) at ../misc/syslog.c:167
4 0x00007fd35382d1e3 in __syslog_chk (pri=pri at entry=3, flag=flag at entry=1, fmt=fmt at entry=0x5560190522da "%s") at ../misc/syslog.c:129
5 0x000055601904e114 in syslog (__fmt=0x5560190522da "%s", __pri=3) at /usr/include/bits/syslog.h:31
6 log_level (name_in=<optimized out>, level_in=<optimized out>, fmt=0x55601905243e "abandoned lockspace %s") at logging.c:166
7 0x000055601903a91e in loop () at main.c:1597
8 main (argc=<optimized out>, argv=<optimized out>) at main.c:2161
We see that the last thing in dlm_controld was log_level() then it
crashed internal handling of libc and syslog().
(gdb) f 6
6 log_level (name_in=<optimized out>, level_in=<optimized out>, fmt=0x55601905243e "abandoned lockspace %s") at logging.c:166
166 syslog(level, "%s", log_str);
We see that log_level() was called with a format string of "abandoned
lockspace %s" and we only do that after leaving the main loop,
dlm_controld was going to shutdown and crashed.
The reason is that at this time the syslog logging was already closed by
closelog() and we still tried to call syslog() and libc doesn't like it.
We should be sure closing the log functionality is the last thing to do
when exiting dlm_controld. This patch is doing that so that dlm_controld
should not crash anymore.
Reported-by: Barry Marson <bmarson@redhat.com>
---
v2:
- remove sob.
dlm_controld/main.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/dlm_controld/main.c b/dlm_controld/main.c
index 80fe14bd..7cf6348e 100644
--- a/dlm_controld/main.c
+++ b/dlm_controld/main.c
@@ -1604,12 +1604,14 @@ static int loop(void)
close_plocks();
close_cpg_daemon();
clear_configfs();
- close_logging();
close_cluster();
close_cluster_cfg();
list_for_each_entry(ls, &lockspaces, list)
log_error("abandoned lockspace %s", ls->name);
+
+ /* must be end */
+ close_logging();
return rv;
}
--
2.31.1
next reply other threads:[~2022-10-05 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:23 Alexander Aring [this message]
2022-10-05 19:23 ` [Cluster-devel] [PATCHv2 dlm-tool 2/2] dlm_controld: fix rare off by one Alexander Aring
2022-10-06 12:45 ` Alexander Aring
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=20221005192312.4130838-1-aahringo@redhat.com \
--to=aahringo@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).