From: Steven Rostedt <srostedt@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Indan Zupancic <indan@nul.nu>, Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix race in ring_buffer_consume(): Replace ring_buffer_consume and ring_buffer_peek with ring_buffer_get_event
Date: Sat, 03 Jan 2009 18:55:17 -0500 [thread overview]
Message-ID: <1231026917.15476.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20090102220818.GD17240@elte.hu>
On Fri, 2009-01-02 at 23:08 +0100, Ingo Molnar wrote:
> * Indan Zupancic <indan@nul.nu> wrote:
>
> > On Mon, December 29, 2008 13:24, Ingo Molnar wrote:
> > >
> > > * Indan Zupancic <indan@nul.nu> wrote:
> > >
> > >> Original mail was mangled, patch resent via git.
> > >>
> > >> Signed-off-by: Indan Zupancic <indan@nul.nu>
> > >> ---
> > >> include/linux/ring_buffer.h | 4 +---
> > >> kernel/trace/ring_buffer.c | 39
> > >> ++++++++-------------------------------
> > >> kernel/trace/trace.c | 15 ++++++++-------
> > >> kernel/trace/trace_selftest.c | 2 +-
> > >> 4 files changed, 18 insertions(+), 42 deletions(-)
> > >
> > > there's been a number of updates here - could you please do a patch
> > > against tip/master:
> > >
> > > http://people.redhat.com/mingo/tip.git/README
> >
> > Thanks for that readme, now I discovered git remote, which is not
> > mentioned often enough for some reason.
> >
> > A lot changed indeed, most importantly the race that I hit is
> > fixed in tip by improved locking. Replace ring_buffer_consume()
> > and ring_buffer_peek() with ring_buffer_get_event() or not is
> > just a matter of taste now. Are you still interested in such a
> > patch?
>
> the code gets simpler and more readable, so why not? Steve, any
> objections?
I'd like to look closer at this code on Monday.
Thanks,
-- Steve
next prev parent reply other threads:[~2009-01-03 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 3:59 [PATCH] Fix race in ring_buffer_consume() Indan Zupancic
2008-12-29 7:34 ` [PATCH] Fix race in ring_buffer_consume(): Replace ring_buffer_consume and ring_buffer_peek with ring_buffer_get_event Indan Zupancic
2008-12-29 12:24 ` Ingo Molnar
2009-01-01 5:10 ` Indan Zupancic
2009-01-02 22:08 ` Ingo Molnar
2009-01-03 23:55 ` Steven Rostedt [this message]
2009-01-05 15:09 ` Steven Rostedt
2009-01-11 8:35 ` [PATCH] Minor cleanups in ring_buffer.c Indan Zupancic
2009-01-11 8:46 ` [PATCH] Minor cleanups in ring_buffer.c, try 2 Indan Zupancic
2009-01-11 9:49 ` [PATCH] Fix race in ring_buffer_consume(): Replace ring_buffer_consume and ring_buffer_peek with ring_buffer_get_event Indan Zupancic
2008-12-29 14:47 ` [PATCH] Fix race in ring_buffer_consume() 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=1231026917.15476.0.camel@localhost.localdomain \
--to=srostedt@redhat.com \
--cc=indan@nul.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
Powered by JetHome