linux-kernel - Re: LTTng kernel integration roadmap, update

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]

Message-ID: <20081124114124.GA32459@infradead.org>
Date:	Mon, 24 Nov 2008 06:41:24 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Mathieu Desnoyers <compudj@...stal.dyndns.org>
Cc:	ltt-dev@...ts.casi.polymtl.ca, Zhaolei <zhaolei@...fujitsu.com>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Ingo Molnar <mingo@...e.hu>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org
Subject: Re: LTTng kernel integration roadmap, update

On Mon, Nov 24, 2008 at 06:28:42AM -0500, Mathieu Desnoyers wrote:
> - trimmed-down lttv for the kernel tree
>   Need to look at
>   git://git.kernel.org/pub/scm/linux/kernel/git/sam/test.git#master
>   tests/ directory, which permits building userspace tools with the
>   Linux kernel. I recently got the idea of populating debugfs with
>   userspace tools that would sits in kernel module data. How (in)sane
>   does this idea look ? That would seems like a rather good solution to
>   ship the userspace tool with the kernel.

Completely insane I'd say.  Debugfs is per defintion populated from
kernelspace, and adding another mixed user/kernel populated fs like
devfs is a rather bad idea.  I don't quite see any point in shipping
lttv with the kernel tree either, it shouldn't really need knowledge of
the kernel version.

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