{"head":"f6ce8b1945431efc69d4d9b9b02f73af98edbe53","size":1,"push_id":46572225,"ref":"refs/heads/master","commits":[{"sha":"f6ce8b1945431efc69d4d9b9b02f73af98edbe53","author":{"name":"Antonio Huete Jimenez","email":"5af63352924aee0d35c7a5e28ee9a80777cf71af@quantumachine.net"},"url":"https://api.github.com/repos/DragonFlyBSD/DragonFlyBSD/commits/f6ce8b1945431efc69d4d9b9b02f73af98edbe53","message":"syscons - Avoid potential blocking issue.\n\n- kbd_ioctl() uses it's own locking via lockmgr() and the\n  syscons softc is protected using a mutex, so we better\n  avoid both locks at once due possible blocking issues.\n  In fact, in my particular case the panic only occurs in\n  real hardware, while on a VMWare VM I had a lockup.\n- Only found in 4-CPU SMP setups.\n- Discovered via DEBUG_LOCKS option.\n\nDragonFly-bug: <http://bugs.dragonflybsd.org/issue2148>\nReviewed-by: @dillon, @sjg"}],"legacy":{"head":"f6ce8b1945431efc69d4d9b9b02f73af98edbe53","size":1,"push_id":46572225,"shas":[["f6ce8b1945431efc69d4d9b9b02f73af98edbe53","tuxillo@quantumachine.net","syscons - Avoid potential blocking issue.\n\n- kbd_ioctl() uses it's own locking via lockmgr() and the\n  syscons softc is protected using a mutex, so we better\n  avoid both locks at once due possible blocking issues.\n  In fact, in my particular case the panic only occurs in\n  real hardware, while on a VMWare VM I had a lockup.\n- Only found in 4-CPU SMP setups.\n- Discovered via DEBUG_LOCKS option.\n\nDragonFly-bug: <http://bugs.dragonflybsd.org/issue2148>\nReviewed-by: @dillon, @sjg","Antonio Huete Jimenez"]],"ref":"refs/heads/master"}}