From: Steven Rostedt <rostedt@goodmis.org>
To: Vasily Gorbik <gor@linux.ibm.com>
Cc: Josef Bacik <jbacik@fb.com>, linux-kernel@vger.kernel.org
Subject: Re: User stacktrace garbage when USER_STACKTRACE_SUPPORT is not enabled
Date: Wed, 31 Mar 2021 18:27:20 -0400 [thread overview]
Message-ID: <20210331182720.51f41b89@oasis.local.home> (raw)
In-Reply-To: <your-ad-here.call-01617228177-ext-4428@work.hours>
On Thu, 1 Apr 2021 00:02:57 +0200
Vasily Gorbik <gor@linux.ibm.com> wrote:
> I only tested it on s390 (manually + ftrace selftest), quite frankly.
> If it qualifies:
You reported the bug, thus tested-by from the reporter always
qualifies ;-)
>
> Tested-by: Vasily Gorbik <gor@linux.ibm.com> # s390 only
Thanks,
-- Steve
prev parent reply other threads:[~2021-03-31 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 11:52 User stacktrace garbage when USER_STACKTRACE_SUPPORT is not enabled Vasily Gorbik
2021-03-31 14:37 ` Steven Rostedt
2021-03-31 20:51 ` Vasily Gorbik
2021-03-31 21:09 ` Steven Rostedt
2021-03-31 22:02 ` Vasily Gorbik
2021-03-31 22:27 ` Steven Rostedt [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=20210331182720.51f41b89@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=gor@linux.ibm.com \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).