From: Andrew Morton <akpm@osdl.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Ingo Molnar <mingo@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, ltt-dev@shafik.org,
"Martin J. Bligh" <mbligh@mbligh.org>,
Douglas Niehaus <niehaus@eecs.ku.edu>,
systemtap@sources.redhat.com,
Thomas Gleixner <tglx@linutronix.de>,
Richard J Moore <richardj_moore@uk.ibm.com>
Subject: Re: [PATCH 1/2] lockdep missing barrier()
Date: Wed, 24 Jan 2007 04:28:00 -0000 [thread overview]
Message-ID: <20070123202637.970e467b.akpm@osdl.org> (raw)
In-Reply-To: <20070116175624.GA16022@Krystal>
On Tue, 16 Jan 2007 12:56:24 -0500
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> This patch adds a barrier() to lockdep.c lockdep_recursion updates. This
> variable behaves like the preemption count and should therefore use similar
> memory barriers.
>
> This patch applies on 2.6.20-rc4-git3.
>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
>
> --- a/kernel/lockdep.c
> +++ b/kernel/lockdep.c
> @@ -166,12 +166,14 @@ static struct list_head chainhash_table[CHAINHASH_SIZE];
> void lockdep_off(void)
> {
> current->lockdep_recursion++;
> + barrier();
> }
>
> EXPORT_SYMBOL(lockdep_off);
>
> void lockdep_on(void)
> {
> + barrier();
> current->lockdep_recursion--;
> }
I am allergic to undocumented barriers. It is often unobvious what the
barrier is supposed to protect against, yielding mystifying code. This is
one such case.
Please add code comments.
next prev parent reply other threads:[~2007-01-24 4:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 0:01 [PATCH 0/4] Linux Kernel Markers Mathieu Desnoyers
2006-12-21 0:01 ` [PATCH 2/4] Linux Kernel Markers : kconfig menus Mathieu Desnoyers
2006-12-21 0:03 ` [PATCH 3/4] Linux Kernel Markers : i386 optimisation Mathieu Desnoyers
2006-12-21 0:04 ` [PATCH 4/4] Linux Kernel Markers : powerpc optimisation Mathieu Desnoyers
2006-12-21 0:07 ` [PATCH 1/4] Linux Kernel Markers : Architecture agnostic code Mathieu Desnoyers
2007-01-13 1:33 ` [PATCH 0/4] Linux Kernel Markers Richard J Moore
2007-01-13 5:51 ` Mathieu Desnoyers
2007-01-16 17:47 ` [PATCH 0/4 update] Linux Kernel Markers - i386 : pIII erratum 49 : XMC Mathieu Desnoyers
2007-01-16 18:35 ` Frank Ch. Eigler
2007-01-16 21:28 ` [PATCH 0/4 update] kprobes and traps Mathieu Desnoyers
2007-01-17 12:26 ` S. P. Prasanna
2007-01-16 18:01 ` [PATCH 2/2] lockdep reentrancy Mathieu Desnoyers
2007-01-24 4:30 ` Andrew Morton
2007-01-24 17:05 ` Mathieu Desnoyers
2007-01-16 18:06 ` [PATCH 1/2] lockdep missing barrier() Mathieu Desnoyers
2007-01-24 4:28 ` Andrew Morton [this message]
2007-01-24 17:02 ` Mathieu Desnoyers
2007-01-24 17:30 ` [PATCH] order of lockdep off/on in vprintk() should be changed Mathieu Desnoyers
2007-01-24 18:01 ` [PATCH] minimize lockdep_on/off side-effect Mathieu Desnoyers
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=20070123202637.970e467b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@mbligh.org \
--cc=mingo@redhat.com \
--cc=niehaus@eecs.ku.edu \
--cc=richardj_moore@uk.ibm.com \
--cc=systemtap@sources.redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).