mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCH 0/2] irq_work: A couple fixes
Date: Tue, 30 Oct 2012 16:34:59 +0100	[thread overview]
Message-ID: <1351611301-3520-1-git-send-email-fweisbec@gmail.com> (raw)

Hi,

The first patch is extracted from my printk patches, with changelog
reworked. The second patch is an addition.

And I still wonder if cpu_relax() is enough to prevent the compiler
from correctly reloading work->flags in irq_work_sync() loop.
Do we need ACCESS_ONCE()?

Thanks.

Frederic Weisbecker (2):
  irq_work: Fix racy check on work pending flag
  irq_work: Fix racy IRQ_WORK_BUSY flag setting

 kernel/irq_work.c |   29 ++++++++++++++++++++++-------
 1 files changed, 22 insertions(+), 7 deletions(-)

-- 
1.7.5.4


             reply	other threads:[~2012-10-30 15:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 15:34 Frederic Weisbecker [this message]
2012-10-30 15:35 ` [PATCH 1/2] irq_work: Fix racy check on work pending flag Frederic Weisbecker
2012-10-30 15:53   ` Steven Rostedt
2012-10-30 15:35 ` [PATCH 2/2] irq_work: Fix racy IRQ_WORK_BUSY flag setting Frederic Weisbecker
2012-10-30 16:26   ` Steven Rostedt
2012-10-30 18:33   ` anish kumar
2012-10-30 18:45     ` Steven Rostedt
2012-10-31 11:06       ` anish kumar
2012-10-31  0:36     ` Frederic Weisbecker
2012-10-31  2:23       ` Steven Rostedt
2012-10-31  2:54         ` Frederic Weisbecker
2012-10-31 11:04         ` anish kumar
2012-10-31 12:59           ` Steven Rostedt
2012-10-31 13:32             ` Frederic Weisbecker
2012-10-31 13:51           ` Steven Rostedt
2012-10-30 15:52 ` [PATCH 0/2] irq_work: A couple fixes Steven Rostedt
2012-10-30 16:25   ` Frederic Weisbecker
2012-10-30 17:13     ` Steven Rostedt
2012-10-30 17:17       ` 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=1351611301-3520-1-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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
all inboxes | Powered by JetHome®