From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: Miroslav Benes <mbenes@suse.cz>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
live-patching@vger.kernel.org
Subject: Re: stack traces and zombie tasks
Date: Sun, 17 Dec 2017 21:34:08 -0600 [thread overview]
Message-ID: <20171218033408.whh7bkqfuaolrldm@treble> (raw)
In-Reply-To: <CALCETrXUrDXZ_aXC-iaN7757jFSkS0JaFOz2b9rEsVKuNUshyA@mail.gmail.com>
On Fri, Dec 15, 2017 at 07:51:45AM -0800, Andy Lutomirski wrote:
> On Fri, Dec 15, 2017 at 4:54 AM, Miroslav Benes <mbenes@suse.cz> wrote:
> > Hi,
> >
> > commit 1959a60182f4 ("x86/dumpstack: Pin the target stack when dumping
> > it") slightly changed the behaviour of stack traces dumping for zombie
> > tasks.
> >
> > Before the commit (well, this is older SLE12 kernel, but that should not
> > matter), if one called 'cat /proc/<zombie pid>/stack', they would get
> > something like this
> >
> > [<ffffffff8105b877>] do_exit+0x6f7/0xa80
> > [<ffffffff8105bc79>] do_group_exit+0x39/0xa0
> > [<ffffffff8105bcf0>] __wake_up_parent+0x0/0x30
> > [<ffffffff8152dd09>] system_call_fastpath+0x16/0x1b
> > [<00007fd128f9c4f9>] 0x7fd128f9c4f9
> > [<ffffffffffffffff>] 0xffffffffffffffff
> >
> > After, one gets nothing. The trace is empty. try_get_task_stack() contains
> > atomic_inc_not_zero() (CONFIG_THREAD_INFO_IN_TASK is now default on
> > x86_64) and because stack_refcount is 0 for a zombie task, it returns
> > NULL. Therefore, all save_stack_trace_*() functions return immediately.
> >
> > I guess that no one has cared about it so far. There is a problem for
> > live patching though. save_stack_trace_tsk_reliable() returns -EINVAL for
> > the zombie task and its stack is deemed unreliable. It could block our
> > transition for quite a long time.
> >
> > We can skip those tasks in kernel/livepatch/ with a simple test we have in
> > kGraft. Skip the task if (task->state == TASK_DEAD && task->on_cpu == 0).
> > But you may want to change it generally, so better to ask first.
> >
>
> Sounds like a bug in save_stack_trace_tsk_reliable() to me: if the
> task has no stack, then the trace is 100% definitely empty :)
I would agree with that, something like the following should fix it?
diff --git a/arch/x86/kernel/stacktrace.c b/arch/x86/kernel/stacktrace.c
index 77835bc021c7..20161ef53537 100644
--- a/arch/x86/kernel/stacktrace.c
+++ b/arch/x86/kernel/stacktrace.c
@@ -164,8 +164,12 @@ int save_stack_trace_tsk_reliable(struct task_struct *tsk,
{
int ret;
+ /*
+ * If the task doesn't have a stack (e.g., a zombie), the stack is
+ * "reliably" empty.
+ */
if (!try_get_task_stack(tsk))
- return -EINVAL;
+ return 0;
ret = __save_stack_trace_reliable(trace, tsk);
next prev parent reply other threads:[~2017-12-18 3:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 12:54 Miroslav Benes
2017-12-15 15:51 ` Andy Lutomirski
2017-12-18 3:34 ` Josh Poimboeuf [this message]
2017-12-18 13:07 ` Miroslav Benes
2017-12-19 7:50 ` Ingo Molnar
2017-12-19 8:00 ` Ingo Molnar
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=20171218033408.whh7bkqfuaolrldm@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mbenes@suse.cz \
--cc=x86@kernel.org \
/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®