From: Steven Rostedt <rostedt@goodmis.org>
To: Zheng Yejian <zhengyejian1@huawei.com>
Cc: <mhiramat@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH] ring-buffer: Fix deadloop issue on reading trace_pipe
Date: Wed, 12 Jul 2023 12:14:48 -0400 [thread overview]
Message-ID: <20230712121448.628ad188@gandalf.local.home> (raw)
In-Reply-To: <63ff741f-b781-37da-3f47-15d1a8ff76a4@huawei.com>
On Mon, 10 Jul 2023 09:37:52 +0800
Zheng Yejian <zhengyejian1@huawei.com> wrote:
> teve, IIUC, following tags should be added?
>
> Cc: stable@vger.kernel.org
> Fixes: 48fdc72f23ad ("ring-buffer: Fix accounting of entries when
> removing pages")
> Fixes: 83f40318dab0 ("ring-buffer: Make removal of ring buffer pages
> atomic")
I actually added:
Fixes: a5fb833172eca ("ring-buffer: Fix uninitialized read_stamp")
-- Steve
next prev parent reply other threads:[~2023-07-12 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 22:51 [PATCH] ring-buffer: Fix deadloop issue on reading trace_pipe Zheng Yejian
2023-07-09 19:45 ` Steven Rostedt
2023-07-10 1:37 ` Zheng Yejian
2023-07-12 16:14 ` Steven Rostedt [this message]
2023-07-13 1:52 ` Zheng Yejian
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=20230712121448.628ad188@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=zhengyejian1@huawei.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