| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 30 Apr 2012 10:44:21 +0200 (CEST) From: Jiri Kosina <jkosina@...e.cz> To: Henrik Rydberg <rydberg@...omail.se> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 0/6] hid: Introduce device groups On Mon, 30 Apr 2012, Jiri Kosina wrote: > > Here is the third version of the extension to the device-driver > > matching mechanism. AFAICT, there are no outstanding issues. I think > > we are getting close. :-) > > I think so, and overall I like the aproach and the implementation. Thanks! > > Just got the stacktrace on [1] though when running kernel with this > patchset. The trace popped during shutdown, and the machine froze > completely; I didn't have any kind of external console connected, so > unfortunately I don't have the beginning of the whole thing. > > I haven't been able to reproduce it so far. This was after several > "parallel" plug/remove cycles of multiple HID devices driven by multiple > different drivers. > > I haven't performed any analysis what this might be yet. > > [1] http://www.jikos.cz/jikos/junk/autoloading-trace.jpg It actually seems to be spinlock lockup (due to the NMI trigger being apparent at the very first line) on kbd_event_lock ... -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists