From: Corey Minyard <minyard@acm.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Carol Hebert <cah@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Developers <openipmi-developer@lists.sourceforge.net>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
OpenIPMI@sc8-sf-spam2-b.sourceforge.net
Subject: Re: [Openipmi-developer] [PATCH] IPMI: Fix some RCU problems
Date: Wed, 3 Jan 2007 21:34:40 -0600 [thread overview]
Message-ID: <20070104033440.GA27532@localdomain> (raw)
In-Reply-To: <20070103132232.f924227e.akpm@osdl.org>
On Wed, Jan 03, 2007 at 01:22:32PM -0800, Andrew Morton wrote:
> It's nice to always have a comment explaining the use of open-coded
> barriers. Because often the reader is left wondered what on earth it's
> barriering against what on earth else.
>
Ok, here it is...
Andrew asked that the open-coded barriers be commented, so here it
is. I also realized that one of the read barriers was in an area
where the protecting mutex was held, so no read barrier was needed.
Signed-off-by: Corey Minyard <minyard@acm.org>
Index: linux-2.6.19/drivers/char/ipmi/ipmi_msghandler.c
===================================================================
--- linux-2.6.19.orig/drivers/char/ipmi/ipmi_msghandler.c
+++ linux-2.6.19/drivers/char/ipmi/ipmi_msghandler.c
@@ -839,7 +839,6 @@ int ipmi_create_user(unsigned int
goto out_kfree;
found:
- smp_rmb();
/* Note that each existing user holds a refcount to the interface. */
kref_get(&intf->refcount);
@@ -2762,10 +2761,15 @@ int ipmi_register_smi(struct ipmi_smi_ha
synchronize_rcu();
kref_put(&intf->refcount, intf_free);
} else {
- /* After this point the interface is legal to use. */
- smp_wmb(); /* Keep memory order straight for RCU readers. */
+ /*
+ * Keep memory order straight for RCU readers. Make
+ * sure everything else is committed to memory before
+ * setting intf_num to mark the interface valid.
+ */
+ smp_wmb();
intf->intf_num = i;
mutex_unlock(&ipmi_interfaces_mutex);
+ /* After this point the interface is legal to use. */
call_smi_watchers(i, intf->si_dev);
mutex_unlock(&smi_watchers_mutex);
}
@@ -3927,6 +3931,12 @@ static void send_panic_events(char *str)
/* Interface was not ready yet. */
continue;
+ /*
+ * intf_num is used as an marker to tell if the
+ * interface is valid. Thus we need a read barrier to
+ * make sure data fetched before checking intf_num
+ * won't be used.
+ */
smp_rmb();
/* First job here is to figure out where to send the
prev parent reply other threads:[~2007-01-04 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 15:31 [PATCH] IPMI: Fix some RCU problems Corey Minyard
2007-01-03 21:22 ` Andrew Morton
2007-01-04 3:34 ` Corey Minyard [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=20070104033440.GA27532@localdomain \
--to=minyard@acm.org \
--cc=OpenIPMI@sc8-sf-spam2-b.sourceforge.net \
--cc=akpm@osdl.org \
--cc=cah@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=paulmck@linux.vnet.ibm.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