Subject: kern/30233: raidstrategy() isn't interrupt-safe
To: None <email@example.com, firstname.lastname@example.org,>
From: Manuel Bouyer <email@example.com>
Date: 05/14/2005 22:03:00
>Synopsis: raidstrategy() isn't interrupt-safe
>Arrival-Date: Sat May 14 22:03:00 +0000 2005
>Originator: Manuel Bouyer
>Release: NetBSD 3.99.3
System: NetBSD rochebonne.antioche.eu.org 3.99.3 NetBSD 3.99.3 (ROCHEBONNE) #0: Sat May 14 15:33:21 CEST 2005 firstname.lastname@example.org:/local/pop1/bouyer/tmp/i386/obj/local/pop1/bouyer/current/src/sys/arch/i386/compile/ROCHEBONNE i386
Quoting a post from Jason Thorpe on tech-kern:
> There are lots of other things that might cause a disk's strategy
> routine to be called from interrupt context (ccd / raidframe are good
> examples). Really, we need to audit ALL of the disk strategy
> routines and ensure that they are IPL_BIO interrupt-context safe.
raidstrategy() isn't safe to call from interrupt context: it ends up
There may be other problems too other problems when called from
interrupt context too (are the locks interrupt-safe ?).
An easy way to trigger a pool_get() panic is to export a partition
from a raidframe device to a guest Xen domain, as reported by
Yoshito Komatsu on port-xen.