Ed Cashin a0e0e463b1 aoe: do not call bdi_init after blk_alloc_queue ... commit 0a41409c51 upstream, but doesn't apply, so this version is different for older kernels than 3.7.x blk_alloc_queue has already done a bdi_init, so do not bdi_init again in aoeblk_gdalloc. The extra call causes list corruption in the per-CPU backing dev info stats lists. Affected users see console WARNINGs about list_del corruption on percpu_counter_destroy when doing "rmmod aoe" or "aoeflush -a" when AoE targets have been detected and initialized by the system. The patch below applies to v3.6.11, with its v47 aoe driver. It is expected to apply to all currently maintained stable kernels except 3.7.y. A related but different fix has been posted for 3.7.y. References: RedHat bugzilla ticket with original report https://bugzilla.redhat.com/show_bug.cgi?id=853064 LKML discussion of bug and fix http://thread.gmane.org/gmane.linux.kernel/1416336/focus=1416497 Reported-by: Josh Boyer <jwboyer@redhat.com> Signed-off-by: Ed Cashin <ecashin@coraid.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2013-01-17 08:50:53 -08:00
..
aoe.h	aoe: do not call bdi_init after blk_alloc_queue	2013-01-17 08:50:53 -08:00
aoeblk.c	aoe: do not call bdi_init after blk_alloc_queue	2013-01-17 08:50:53 -08:00
aoechr.c	switch device_get_devnode() and ->devnode() to umode_t *	2012-01-03 22:54:55 -05:00
aoecmd.c	aoe: assert AoE packets marked as requiring no checksum	2012-10-13 05:38:46 +09:00
aoedev.c
aoemain.c
aoenet.c
Makefile	drivers/block/aoe/Makefile: replace the use of <module>-objs with <module>-y	2011-01-19 08:25:02 -07:00