From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Denys Vlasenko <dvlasenk@redhat.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Mark Wielaard <mjw@redhat.com>,
Martin Milata <mmilata@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] coredump: add %i/%I in core_pattern to report the tid of the crashed thread
Date: Tue, 23 Sep 2014 16:05:51 -0700 [thread overview]
Message-ID: <20140923160551.8e93a39f10a818684a514cf2@linux-foundation.org> (raw)
In-Reply-To: <20140922171525.GA32171@redhat.com>
On Mon, 22 Sep 2014 19:15:25 +0200 Oleg Nesterov <oleg@redhat.com> wrote:
> format_corename() can only pass the leader's pid to the core handler, but
> there is no simple way to figure out which thread originated the coredump.
>
> As Jan explains, this also means that there is no simple way to create the
> backtrace of the crashed process:
>
> As programs are mostly compiled with implicit gcc -fomit-frame-pointer one
> needs program's .eh_frame section (equivalently PT_GNU_EH_FRAME segment) or
> .debug_frame section. .debug_frame usually is present only in separate debug
> info files usually not even installed on the system. While .eh_frame is a
> part of the executable/library (and it is even always mapped for C++
> exceptions unwinding) it no longer has to be present anywhere on the disk
> as the program could be upgraded in the meantime and the running instance
> has its executable file already unlinked from disk.
>
> One possibility is to echo 0x3f >/proc/*/coredump_filter and dump all the
> file-backed memory including the executable's .eh_frame section. But that
> can create huge core files, for example even due to mmapped data files.
>
> Other possibility would be to read .eh_frame from /proc/PID/mem at the
> core_pattern handler time of the core dump. For the backtrace one needs to
> read the register state first which can be done from core_pattern handler:
>
> ptrace(PTRACE_SEIZE, tid, 0, PTRACE_O_TRACEEXIT)
> close(0); // close pipe fd to resume the sleeping dumper
> waitpid(); // should report EXIT
> PTRACE_GETREGS or other requests
>
> The remaining problem is how to get the 'tid' value of the crashed thread.
> It could be read from the first NT_PRSTATUS note of the core file but that
> makes the core_pattern handler complicated.
>
> Unfortunately %t is already used so this patch uses %i/%I.
Is any userspace actually going to use this? If so, details?
Am wondering what is driving this change...
next prev parent reply other threads:[~2014-09-23 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 17:53 [PATCH] coredump: add %T in core_pattern to report the tid Oleg Nesterov
2014-09-22 15:22 ` Oleg Nesterov
2014-09-22 17:15 ` [PATCH v2] coredump: add %i/%I in core_pattern to report the tid of the crashed thread Oleg Nesterov
2014-09-23 23:05 ` Andrew Morton [this message]
2014-09-24 9:12 ` Martin Milata
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=20140923160551.8e93a39f10a818684a514cf2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dvlasenk@redhat.com \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjw@redhat.com \
--cc=mmilata@redhat.com \
--cc=oleg@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®