| 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: Wed, 3 Sep 2014 21:24:10 +0200 From: Daniel Vetter <daniel.vetter@...ll.ch> To: Johannes Berg <johannes@...solutions.net> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Seth Forshee <seth.forshee@...onical.com>, Emmanuel Grumbach <emmanuel.grumbach@...el.com>, luca@...lho.fi, kvalo@...rom.com Subject: Re: [RFC] firmware coredump: add new firmware coredump class On Wed, Sep 3, 2014 at 9:05 PM, Johannes Berg <johannes@...solutions.net> wrote: > >> And if we want to use this for i915 we need some way for tools to go >> from the i915 drm class device node to the error state, not just from >> the error state back to the device. > > Interesting. That's probably not all that difficult to do (maybe even > set up a child/parent relationship?) but I actually wanted to avoid a > hard dependency since there may be cases where the failing device > disappears, e.g. in the case of USB. I have to think about this case > more, I guess. Yeah a hard parent/child won't because the device might drop off the bus while committing seppuku. But I think we need to be able to follow the link both ways. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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