From: Ingo Molnar <mingo@kernel.org>
To: Miroslav Benes <mbenes@suse.cz>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Andy Lutomirski <luto@kernel.org>, 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: Tue, 19 Dec 2017 09:00:28 +0100 [thread overview]
Message-ID: <20171219080028.mqeq2spo67kihuou@gmail.com> (raw)
In-Reply-To: <20171219075026.hlczgvqnsfligmg7@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
> > This obviously fixes the problem, so you can add
> >
> > Reported-and-tested-by: Miroslav Benes <mbenes@suse.cz>
>
> Great.
>
> Josh, mind sending a changelogged version, or should I distill a commit out of
> this discussion, for tip:x86/urgent?
... never mind, later in my mbox I found the patch that Josh already submitted!
Thanks,
Ingo
prev parent reply other threads:[~2017-12-19 8:00 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
2017-12-18 13:07 ` Miroslav Benes
2017-12-19 7:50 ` Ingo Molnar
2017-12-19 8:00 ` Ingo Molnar [this message]
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=20171219080028.mqeq2spo67kihuou@gmail.com \
--to=mingo@kernel.org \
--cc=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
Powered by JetHome