From: Vasily Gorbik <gor@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Josef Bacik <jbacik@fb.com>, linux-kernel@vger.kernel.org
Subject: Re: User stacktrace garbage when USER_STACKTRACE_SUPPORT is not enabled
Date: Thu, 1 Apr 2021 00:02:57 +0200 [thread overview]
Message-ID: <your-ad-here.call-01617228177-ext-4428@work.hours> (raw)
In-Reply-To: <20210331170900.5f41bcd7@gandalf.local.home>
On Wed, Mar 31, 2021 at 05:09:00PM -0400, Steven Rostedt wrote:
> On Wed, 31 Mar 2021 22:51:15 +0200
> Vasily Gorbik <gor@linux.ibm.com> wrote:
>
> > It does! Thanks for the explanation and for the fix. I wonder why nobody
> > noticed and complained about that since v5.6.
>
> Because it didn't lose data, just added extra junk.
>
> >
> > Acked-by: Vasily Gorbik <gor@linux.ibm.com>
>
> Want to give a "tested-by" too?
I only tested it on s390 (manually + ftrace selftest), quite frankly.
If it qualifies:
Tested-by: Vasily Gorbik <gor@linux.ibm.com> # s390 only
next prev parent reply other threads:[~2021-03-31 22:04 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 [this message]
2021-03-31 22:27 ` Steven Rostedt
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=your-ad-here.call-01617228177-ext-4428@work.hours \
--to=gor@linux.ibm.com \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.