linux-kernel - Re: [RFC Patch 1/1] debugfs_printk and debugfs

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:	Wed, 16 Apr 2008 14:25:18 -0700
From:	David Wilder <dwilder@...ibm.com>
To:	prasad@...ux.vnet.ibm.com
CC:	linux-kernel@...r.kernel.org, mathieu.desnoyers@...ymtl.ca,
	hunt@...hat.com
Subject: Re: [RFC Patch 1/1] debugfs_printk and debugfs_dump interface

K. Prasad wrote:
>

> +
> +struct debugfs_printk_data {
> +	char *parent_dir;
> +	char *dir;
> +	int exists;
> +	int buf_size;
> +	int sub_buf_size;
> +};

How about adding a "flags" field here to hold the trace channel flags. 
Pass the flags through to trace_setup().  This way the caller can 
control the trace options.

Add a description of debugfs_printk() and debugfs_dump() to 
Documentation/trace.txt.
--
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/