From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Liu, Chuansheng" <chuansheng.liu@intel.com>
Subject: Re: [PATCH] bug: Use xchg() to update WARN_ON_ONCE() static variable
Date: Tue, 15 Oct 2013 22:41:30 +0200 [thread overview]
Message-ID: <20131015204129.GD3269@localhost.localdomain> (raw)
In-Reply-To: <20131015163622.55181900@gandalf.local.home>
On Tue, Oct 15, 2013 at 04:36:22PM -0400, Steven Rostedt wrote:
> On Tue, 15 Oct 2013 22:21:36 +0200
> Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > Oh, I have a pending patchset that I worked on a few weeks ago which does that.
> > I did not post it because it made WARN_ONCE using the unlikely text section, but
> > the diffstat was nice.
> >
> > I'm going to post that as RFC just in case.
>
> Oh well, I guess I don't need to work on that anymore ;-)
Well, the idea of setting __warned before the warning is still something we want
to fix seperately I think :)
next prev parent reply other threads:[~2013-10-15 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 19:58 [PATCH] bug: Use xchg() to update WARN_ON_ONCE() static variable Steven Rostedt
2013-10-15 20:12 ` Andrew Morton
2013-10-15 20:21 ` Frederic Weisbecker
2013-10-15 20:36 ` Steven Rostedt
2013-10-15 20:41 ` Frederic Weisbecker [this message]
2013-10-15 20:35 ` Steven Rostedt
2013-10-15 20:18 ` Frederic Weisbecker
2013-10-15 20:25 ` Steven Rostedt
2013-10-15 20:37 ` Frederic Weisbecker
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=20131015204129.GD3269@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chuansheng.liu@intel.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.