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, 08 Feb 2012 22:30:24 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: "Myklebust, Trond" <Trond.Myklebust@...app.com> Cc: Randy Dunlap <rdunlap@...otime.net>, Stephen Rothwell <sfr@...b.auug.org.au>, "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Frederic Weisbecker <fweisbec@...il.com> Subject: Re: linux-next: Tree for Feb 2 (trace/events/sunrpc.h) On Thu, 2012-02-09 at 03:14 +0000, Myklebust, Trond wrote: > Hmm.... How about if we rather take that out of the RPC_DEBUG condition? > I'm assuming that if someone compiles in the tracepoint code, then they > want to be able to do a full trace independently of whether or not they > set CONFIG_SYSCTL. Works for me. > > 8<--------------------------------------------------------------------- > From d051b60dcc3032b71cf8d9b96ac4bf24f12b6dcb Mon Sep 17 00:00:00 2001 > From: Trond Myklebust <Trond.Myklebust@...app.com> > Date: Wed, 8 Feb 2012 22:01:15 -0500 > Subject: [PATCH] SUNRPC: Ensure that we can trace waitqueues when > !defined(CONFIG_SYSCTL) > > The tracepoint code relies on the queue->name being defined in order to > be able to display the name of the waitqueue on which an RPC task is > sleeping. > > Reported-by: Randy Dunlap <rdunlap@...otime.net> > Reported-by: Steven Rostedt <rostedt@...dmis.org> Acked-by: Steven Rostedt <rostedt@...dmis.org> -- Steve > Signed-off-by: Trond Myklebust <Trond.Myklebust@...app.com> > --- > include/linux/sunrpc/debug.h | 3 +++ > include/linux/sunrpc/sched.h | 15 +++++++++++++-- > net/sunrpc/sched.c | 4 +--- > 3 files changed, 17 insertions(+), 5 deletions(-) > -- 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