From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: manfred@colorfullife.com, Nadia.Derbey@bull.net,
miltonm@austin.ibm.com, mingo@elte.hu, akpm@linux-foundation.org,
peterz@infradead.org, lnxninja@linux.vnet.ibm.com, efault@gmx.de,
riel@redhat.com
Subject: [PATCH] make idr_remove_all() do removal -before- free_layer()
Date: Sat, 7 Mar 2009 14:25:11 -0800 [thread overview]
Message-ID: <20090307222511.GA10727@linux.vnet.ibm.com> (raw)
The following patch fixes a problem in the IDR system, where an
idr_remove_all() hands a data element to call_rcu() (via free_layer())
before making that data element inaccessible to new readers. This is
very bad, and results in readers still having a reference to this data
element at the end of the grace period. Tests on large machines that
concurrently map and unmap user-space memory within the same multithreaded
process result in crashes within about five minutes. Applying this
patch increases the kernel's longevity to the three-to-eight-hour range.
There appear to be other similar problems in idr_get_empty_slot() and
sub_remove(), but I fixed the easy one in idr_remove_all() first. It is
therefore no surprise that failures still occur.
(Yes, and I did look at the relevant patch last year without spotting
this one. Goes to show the value of testing as well as code review,
I guess...)
Nadia, Manfred, any thoughts?
Located-by: Milton Miller II <miltonm@austin.ibm.com>
Tested-by: Milton Miller II <miltonm@austin.ibm.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
diff --git a/lib/idr.c b/lib/idr.c
index c11c576..dab4bca 100644
--- a/lib/idr.c
+++ b/lib/idr.c
@@ -449,6 +449,7 @@ void idr_remove_all(struct idr *idp)
n = idp->layers * IDR_BITS;
p = idp->top;
+ rcu_assign_pointer(idp->top, NULL);
max = 1 << n;
id = 0;
@@ -467,7 +468,6 @@ void idr_remove_all(struct idr *idp)
p = *--paa;
}
}
- rcu_assign_pointer(idp->top, NULL);
idp->layers = 0;
}
EXPORT_SYMBOL(idr_remove_all);
----- End forwarded message -----
next reply other threads:[~2009-03-07 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 22:25 Paul E. McKenney [this message]
2009-03-08 15:33 ` [PATCH] make idr_remove_all() do removal -before- free_layer() Ingo Molnar
2009-03-08 19:20 ` Paul E. McKenney
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=20090307222511.GA10727@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lnxninja@linux.vnet.ibm.com \
--cc=manfred@colorfullife.com \
--cc=miltonm@austin.ibm.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=riel@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 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.