From: Steven Rostedt <rostedt@goodmis.org>
To: lijiazi <jqqlijiazi@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
"Jiazi.Li" <jiazi.li@transsion.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] ring-buffer: Add barrire in rb_move_tail
Date: Sat, 8 Oct 2022 08:50:06 -0400 [thread overview]
Message-ID: <20221008085006.01f73f0a@rorschach.local.home> (raw)
In-Reply-To: <20221008012128.GA6772@Jiazi.Li>
On Sat, 8 Oct 2022 09:21:29 +0800
lijiazi <jqqlijiazi@gmail.com> wrote:
> On Fri, Sep 30, 2022 at 05:49:34PM -0400, Steven Rostedt wrote:
> > On Thu, 29 Sep 2022 17:12:01 +0800
> > lijiazi <jqqlijiazi@gmail.com> wrote:
> >
> > > > Actually, that failed my testing (for other reasons), can you try this one?
> > > >
> > > Sure, thank you.
> >
> > Have you had a chance to test this yet?
> >
> > The merge window is about to open, and I have it already tested through all
> > my tests. But I want to hold off pushing it to next until I have a
> > tested-by from you.
> >
> > Thanks!
> >
> > -- Steve
> Sorry for the late reply, I just finished my National Day holiday.
> Up to now, the crash issue has not been reproduced with this patch.
> Thanks!
No problem. Thanks for testing it. And thank you even more for
reporting it. This was a real bug that's been around pretty much from
the beginning and nobody (at least I know of) reported it.
-- Steve
prev parent reply other threads:[~2022-10-08 12:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 12:08 [PATCH] ring-buffer: Add barrire in rb_move_tail Jiazi.Li
2022-09-01 15:13 ` Steven Rostedt
2022-09-02 3:47 ` lijiazi
2022-09-02 12:56 ` Steven Rostedt
2022-09-05 3:23 ` lijiazi
2022-09-06 16:25 ` Steven Rostedt
2022-09-07 3:03 ` lijiazi
2022-09-07 8:13 ` lijiazi
2022-09-15 8:25 ` lijiazi
2022-09-28 14:54 ` Steven Rostedt
2022-09-28 14:59 ` Steven Rostedt
2022-09-28 20:29 ` Steven Rostedt
2022-09-29 9:12 ` lijiazi
2022-09-30 21:49 ` Steven Rostedt
2022-10-08 1:21 ` lijiazi
2022-10-08 12:50 ` Steven Rostedt [this message]
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=20221008085006.01f73f0a@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=jiazi.li@transsion.com \
--cc=jqqlijiazi@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mingo@redhat.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).