From: Steven Rostedt <rostedt@goodmis.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
John 'Warthog9' Hawley <warthog9@kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1
Date: Sat, 25 Jun 2022 13:45:52 -0400 [thread overview]
Message-ID: <20220625134552.08c1a23a@rorschach.local.home> (raw)
In-Reply-To: <3EB14A14-767B-4B66-9B28-97DDE7EECFD2@oracle.com>
On Sat, 25 Jun 2022 17:15:07 +0000
Chuck Lever III <chuck.lever@oracle.com> wrote:
> [root@manet ~]# cat /etc/redhat-release
> Fedora release 35 (Thirty Five)
> [root@manet ~]# trace-cmd version
>
> trace-cmd version 2.9.2 (not-a-git-repo)
Ug, that's very old. Fedora should be shipping 3.1.1 soon.
Right John? ;-)
-- Steve
>
> usage:
> trace-cmd [COMMAND] ...
>
> commands:
> record - record a trace into a trace.dat file
> set - set a ftrace configuration parameter
>
> ...
>
> check-events - parse trace event formats
> dump - read out the meta data from a trace file
>
> [root@manet ~]#
next prev parent reply other threads:[~2022-06-25 17:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 15:22 possible trace_printk() bug in v5.19-rc1 Chuck Lever III
2022-06-16 15:34 ` Steven Rostedt
2022-06-16 15:36 ` Chuck Lever III
2022-06-16 15:43 ` Steven Rostedt
2022-06-16 18:07 ` Chuck Lever III
2022-06-17 19:50 ` Steven Rostedt
2022-06-18 1:28 ` Chuck Lever III
2022-06-20 0:57 ` Chuck Lever III
2022-06-24 18:23 ` Chuck Lever III
2022-06-24 23:08 ` Steven Rostedt
2022-06-25 17:15 ` Chuck Lever III
2022-06-25 17:45 ` Steven Rostedt [this message]
2022-06-25 18:28 ` John 'Warthog9' Hawley
2022-06-26 3:01 ` John 'Warthog9' Hawley
2022-06-27 17:08 ` Chuck Lever III
2022-06-27 17:11 ` Steven Rostedt
2022-06-27 17:19 ` Chuck Lever III
2022-06-27 19:01 ` Steven Rostedt
2022-06-28 15:24 ` Steven Rostedt
2022-06-25 18:50 ` Chuck Lever III
2022-06-25 23:01 ` Steven Rostedt
2022-06-26 17:09 ` Chuck Lever III
2022-06-27 15:43 ` Steven Rostedt
2022-06-27 15:51 ` Chuck Lever III
2022-06-27 16:02 ` Steven Rostedt
2022-06-28 3:59 ` 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=20220625134552.08c1a23a@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog9@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 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.