From: Steven Rostedt <rostedt@goodmis.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: John 'Warthog9' Hawley <warthog9@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1
Date: Mon, 27 Jun 2022 12:02:06 -0400 [thread overview]
Message-ID: <20220627120206.182da050@gandalf.local.home> (raw)
In-Reply-To: <0FA59723-8784-4D28-AB5B-049D605095B4@oracle.com>
On Mon, 27 Jun 2022 15:51:04 +0000
Chuck Lever III <chuck.lever@oracle.com> wrote:
> 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.
But can you just verify that the new ones fix the issue in one of your
builds?
I'm not a fedora maintainer, so I have no control over what they ship. But
if you can prove that the issues you have are resolved when upgrading, then
there's nothing more I can do. It's up to fedora to update the libraries.
If it's still broken in the latest versions, then I can do something. But
without verification, this is just a fedora bug, not an upstream one.
-- Steve
next prev parent reply other threads:[~2022-06-27 16:02 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
2022-06-27 16:02 ` Steven Rostedt [this message]
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=20220627120206.182da050@gandalf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox