From: Thomas Richter <tmricht@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, borntraeger@de.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, heiko.carstens@de.ibm.com
Subject: Re: [PATCH] perf test: Test case 66 broken on s390 (lib/traceevent issue)
Date: Mon, 27 Jan 2020 08:34:23 +0100 [thread overview]
Message-ID: <659928a1-95b3-ed0d-7988-745d92b495d6@linux.ibm.com> (raw)
In-Reply-To: <20200124113610.662f4afb@gandalf.local.home>
On 1/24/20 5:36 PM, Steven Rostedt wrote:
> On Sat, 25 Jan 2020 01:31:53 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
>> Hi Steven and Thomas,
>>
>> On Fri, 24 Jan 2020 10:07:42 -0500
>> Steven Rostedt <rostedt@goodmis.org> wrote:
>>
>>> This looks like a kernel bug, not a libtraceevent parsing bug.
>>
>> Totally agreed. It was my fault to update the print format.
>> Even if still there is a problem on s390, this patch must be
>> applied.
>
> Thanks Masami for looking into it.
>
> Thomas,
>
> Please still test this patch. If it works, I'd like to add a
> Reported-by and Tested-by tag from you.
>
> -- Steve
>
>>
>> Fixes: 88903c464321 ("tracing/probe: Add ustring type for user-space string")
>> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
>>
Steven and Masami,
thanks for the patch, it fixes this issue!
PS: I should have sent this description earlier, would have saved a week of debugging
on my side....
--
Thomas Richter, Dept 3252, IBM s390 Linux Development, Boeblingen, Germany
--
Vorsitzender des Aufsichtsrats: Matthias Hartmann
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2020-01-27 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 7:39 [PATCH] perf test: Test case 66 broken on s390 (lib/traceevent issue) Thomas Richter
2020-01-24 15:07 ` Steven Rostedt
2020-01-24 16:31 ` Masami Hiramatsu
2020-01-24 16:36 ` Steven Rostedt
2020-01-27 7:34 ` Thomas Richter [this message]
2020-01-27 15:55 ` Steven Rostedt
2020-01-30 10:58 ` Arnaldo Carvalho de Melo
2020-01-30 12:54 ` 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=659928a1-95b3-ed0d-7988-745d92b495d6@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sumanthk@linux.ibm.com \
/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).