All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	John 'Warthog9' Hawley <warthog9@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1
Date: Mon, 27 Jun 2022 15:51:04 +0000	[thread overview]
Message-ID: <0FA59723-8784-4D28-AB5B-049D605095B4@oracle.com> (raw)
In-Reply-To: <20220627114340.4d89842b@gandalf.local.home>



> On Jun 27, 2022, at 11:43 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> On Sun, 26 Jun 2022 17:09:31 +0000
> Chuck Lever III <chuck.lever@oracle.com> wrote:
> 
>> [cel@manet lib]$ cd /usr/lib64/
>> [cel@manet lib64]$ ls libtrace*
>> libtracecmd.so.1  libtracecmd.so.1.0.0  libtraceevent.so.1  libtraceevent.so.1.2.1  libtracefs.so.1  libtracefs.so.1.1.1
>> [cel@manet lib64]$
> 
> According to https://trace-cmd.org
> 
> The latest libraries are:
> 
> libtraceevent 1.6.1
> libtracefs 1.4.1
> 
> I'm guessing you may have a buggy version.

I checked with dnf. I have the latest versions provided in
Fedora 35, which is still supported.

I'd like to avoid having to maintain the latest version of
the tool and its libraries by hand on all of my development
systems.

--
Chuck Lever




  reply	other threads:[~2022-06-27 15:51 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
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 [this message]
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=0FA59723-8784-4D28-AB5B-049D605095B4@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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.