| 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: Thu, 17 Apr 2008 18:02:21 -0400 From: fche@...hat.com (Frank Ch. Eigler) To: Peter Zijlstra <a.p.zijlstra@...llo.nl> Cc: prasad@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...e.hu, mathieu.desnoyers@...ymtl.ca Subject: Re: [RFC PATCH 1/2] Marker probes in futex.c Peter Zijlstra <a.p.zijlstra@...llo.nl> writes: > [...] >> If we were to log just the futex_ops, just as you had suggested, >> "Just log: >> >> futex: <uaddr> wait >> futex: <uaddr> wakeup" >> [...] >> If you can specifically point me to information you think would be >> absolutely unnecessary, I can get them out of the trace_mark(). > > I'm thinking everything is superflous; you're basically logging what > strace already gives you But we don't want to run strace just for this stuff. As you probably know, strace involves invasive user-space context-switching between the target and the tracer. > except worse by encoding local variable names and exposing kernel > pointers. The pointers are probably excessive, the and the names don't really matter. What does matter is providing enough information for a problem diagnosis tool & person to reconstruct what the kernel must have been thinking when it did something noteworthy. - FChE -- 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