linux-kernel - Re: ktap inclusion in drivers/staging/?

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: <20131025101006.GA3439@gmail.com>
Date:	Fri, 25 Oct 2013 12:10:06 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	jovi.zhangwei@...wei.com,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Tom Zanussi <tom.zanussi@...ux.intel.com>,
	Namhyung Kim <namhyung@...nel.org>,
	David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...hat.com>
Subject: Re: ktap inclusion in drivers/staging/?


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Thu, Oct 24, 2013 at 9:46 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > But I agree, this should not be just dumped into the staging 
> > tree until the patches themselves have been posted and reviewed.
> 
> Btw, it's not just the commit history. The actual file layout is 
> terminally horrible too. The actual LWN article made it look like 
> ktap was just a user-space tool, and I was thinking that it was 
> like tools/pert/, just in staging.
> 
> But looking at the tree, it looks like parts of it is a kernel 
> module, and parts of it is the user space thing, and it's totally 
> impossible to see which is which, it's just all mixed up in the 
> same directory structure.
> 
> Maybe I misunderstood, but that was my reaction from a very quick 
> look.

Yes, that's what I saw as well. I'd be less worried about it all if 
it was tooling alone, but this is actually mostly kernel side code, 
which was not apparent at all to me either, from the structure of 
it.

Thanks,

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