[PATCH] fix klist semantics for lists which have elements removed on traversal
authorJames Bottomley <James.Bottomley@HansenPartnership.com>
Tue, 6 Sep 2005 23:56:51 +0000 (16:56 -0700)
committerLinus Torvalds <torvalds@g5.osdl.org>
Thu, 8 Sep 2005 01:26:54 +0000 (18:26 -0700)
commit34bb61f9ddabd7a7f909cbfb05592eb775f6662a
tree06232f6fc975bd279236fd8005c7d5528220ec68
parentdf4edad1787bbfa3c9c10824e4f11e9f4a7ec5c6
[PATCH] fix klist semantics for lists which have elements removed on traversal

The problem is that klists claim to provide semantics for safe traversal of
lists which are being modified.  The failure case is when traversal of a
list causes element removal (a fairly common case).  The issue is that
although the list node is refcounted, if it is embedded in an object (which
is universally the case), then the object will be freed regardless of the
klist refcount leading to slab corruption because the klist iterator refers
to the prior element to get the next.

The solution is to make the klist take and release references to the
embedding object meaning that the embedding object won't be released until
the list relinquishes the reference to it.

(akpm: fast-track this because it's needed for the 2.6.13 scsi merge)

Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
drivers/base/bus.c
drivers/base/core.c
drivers/base/driver.c
include/linux/klist.h
lib/klist.c