Fedora kernel spinlock warning

[didierg]

Environment

Linux lx-azerty 2.6.33.1-22.fc13.x86_64 #1 SMP Mon Mar 29 02:05:28 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox-3.1-3.1.6_59338_fedora12-1.x86_64

Error messages in /var/log/messages

Mar 29 12:38:06 lx-azerty kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
Mar 29 12:38:13 lx-azerty kernel:
Mar 29 12:38:13 lx-azerty kernel: =============================================
Mar 29 12:38:13 lx-azerty kernel: [ INFO: possible recursive locking detected ]
Mar 29 12:38:13 lx-azerty kernel: 2.6.33.1-22.fc13.x86_64 #1
Mar 29 12:38:13 lx-azerty kernel: ---------------------------------------------
Mar 29 12:38:13 lx-azerty kernel: VirtualBox/2745 is trying to acquire lock:
Mar 29 12:38:13 lx-azerty kernel: (&(&pThis->Spinlock)->rlock){+.+...}, at: [<ffffffffa030dfde>] RTSpinlockAcquire+0x12/0x14 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel:
Mar 29 12:38:13 lx-azerty kernel: but task is already holding lock:
Mar 29 12:38:13 lx-azerty kernel: (&(&pThis->Spinlock)->rlock){+.+...}, at: [<ffffffffa030dfde>] RTSpinlockAcquire+0x12/0x14 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel:
Mar 29 12:38:13 lx-azerty kernel: other info that might help us debug this:
Mar 29 12:38:13 lx-azerty kernel: 1 lock held by VirtualBox/2745:
Mar 29 12:38:13 lx-azerty kernel: #0:  (&(&pThis->Spinlock)->rlock){+.+...}, at: [<ffffffffa030dfde>] RTSpinlockAcquire+0x12/0x14 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel:
Mar 29 12:38:13 lx-azerty kernel: stack backtrace:
Mar 29 12:38:13 lx-azerty kernel: Pid: 2745, comm: VirtualBox Not tainted 2.6.33.1-22.fc13.x86_64 #1
Mar 29 12:38:13 lx-azerty kernel: Call Trace:
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff8107e96b>] __lock_acquire+0xcb5/0xd2c
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff81071226>] ? sched_clock_cpu+0xc3/0xce
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff8107eabe>] lock_acquire+0xdc/0x102
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa030dfde>] ? RTSpinlockAcquire+0x12/0x14 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff81478a73>] _raw_spin_lock+0x36/0x69
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa030dfde>] ? RTSpinlockAcquire+0x12/0x14 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa030dfde>] RTSpinlockAcquire+0x12/0x14 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa0305742>] SUPR0ObjAddRefEx+0xc0/0x1f9 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa035a299>] g_abExecMemory+0x43259/0x180000 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa0364d5c>] g_abExecMemory+0x4dd1c/0x180000 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa035bf02>] g_abExecMemory+0x44ec2/0x180000 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa0328f14>] g_abExecMemory+0x11ed4/0x180000 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff8107f2b4>] ? lock_release_non_nested+0xd5/0x23b
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa03296a0>] g_abExecMemory+0x12660/0x180000 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa0307d7e>] supdrvIOCtl+0x1098/0x1e52 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff810f1dd5>] ? might_fault+0xa5/0xac
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff810f1d8c>] ? might_fault+0x5c/0xac
Mar 29 12:38:13 lx-azerty kernel: [<ffffffffa0304262>] VBoxDrvLinuxIOCtl+0x124/0x1a7 [vboxdrv]
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff8112c054>] vfs_ioctl+0x32/0xa6
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff8112c5d4>] do_vfs_ioctl+0x490/0x4d6
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff8111fe91>] ? fget_light+0x57/0x105
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff8112c670>] sys_ioctl+0x56/0x79
Mar 29 12:38:13 lx-azerty kernel: [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b