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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 31 Mar 2015 09:26:43 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [RFC][PATCH 00/10] tracing: Use TRACE_DEFINE_ENUM() to show
 enum values

On Tue, 31 Mar 2015 16:36:51 +0900
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:

> > Instead of adding an enum mapping file, I could add a way to look at
> > all the events in the system that defined a mapping, and do a
> > "s/ENUM_NAME/ENUM_VALUE/g" do the saved print formats? I'm not sure how
> > much we want to do that in the kernel though.
> 
> No, it's not what I expected...

Actually, I'm going to play with this idea and see how crazy it is or
isn't. Converting the ENUMS in TP_printk() might actually be doable.

I'll write up some code and we can see if it seems sane or not. OK?


> 
> What I thought was expanding __print_symbolic() macro in TP_printk
> with a special hash string(start with #), and when showing it via
> event/format, replace the hash string with the strings generated
> by the map of symbols. This will introduce a small overhead to show
> the format as a side effect.
> 
> Actually I even have not tried, so it's just an idea yet.
> 

If you can figure something out, please let me know!

Thanks,

-- Steve
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ