From: Jiri Slaby <jslaby@suse.cz>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Miroslav Benes <mbenes@suse.cz>
Subject: Re: [PATCH 1/2] x86/stacktrace: do not fail when regs on stack for ORC
Date: Mon, 18 Dec 2017 07:59:15 +0100 [thread overview]
Message-ID: <0dc9045b-c516-4c6e-23ab-de65c37f7a74@suse.cz> (raw)
In-Reply-To: <20171218033749.ihpwkjh7qfnilj4s@treble>
On 12/18/2017, 04:37 AM, Josh Poimboeuf wrote:
> On Thu, Dec 14, 2017 at 10:58:35PM +0100, Jiri Slaby wrote:
>>> return -EINVAL;
>>
>> Kthreads and idle tasks hit this error as they have no user regs on the
>> stack obviously :).
>
> Doh, sorry, I forgot about that.
FWIW and to be complete, as Mira Benes pointed out in some other thread,
also zombies/dead tasks belong here which have emptied stack.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2017-12-18 6:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 8:03 Jiri Slaby
2017-11-30 8:03 ` [PATCH 2/2] x86/stacktrace: make sure reliable stack trace reached userspace Jiri Slaby
2017-11-30 19:57 ` [PATCH 1/2] x86/stacktrace: do not fail when regs on stack for ORC Josh Poimboeuf
2017-11-30 19:59 ` Josh Poimboeuf
2017-12-01 7:34 ` Jiri Slaby
2017-12-14 21:58 ` Jiri Slaby
2017-12-18 3:37 ` Josh Poimboeuf
2017-12-18 6:59 ` Jiri Slaby [this message]
2017-12-20 17:45 ` Josh Poimboeuf
2017-12-20 19:07 ` Jiri Slaby
2018-04-16 22:16 ` Josh Poimboeuf
2018-04-19 13:42 ` Josh Poimboeuf
2018-05-10 12:33 ` Jiri Slaby
2018-05-10 12:49 ` Josh Poimboeuf
2018-05-11 7:01 ` Jiri Slaby
2018-05-11 15:12 ` Josh Poimboeuf
2018-05-14 11:08 ` Jiri Slaby
2018-05-14 13:42 ` Josh Poimboeuf
2018-05-14 14:00 ` Jiri Slaby
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=0dc9045b-c516-4c6e-23ab-de65c37f7a74@suse.cz \
--to=jslaby@suse.cz \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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®