| 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
| ||
|
Message-ID: <52FA41FA.6030908@ahsoftware.de> Date: Tue, 11 Feb 2014 16:30:02 +0100 From: Alexander Holler <holler@...oftware.de> To: linux-kernel@...r.kernel.org Subject: work unwinding? Hello, Since the kernel has become more RT-aware and many stuff has moved into works, dump_stack() has often become a bit useless, because it just shows the call stack of a work, which quiet often is a bit short and doesn't reveal the real source of a problem. At least I would like it if there would be some mechanism to record the call stack for works, so that dump_stack() could display what actually queued a work (and it's call stack). Not that I want to implement such, I'm just curious if someone already has thought about implementing something like that, which I'm calling here "work unwinding" ;) Regards, Alexander Holler -- 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