linux-kernel - Re: utrace merge

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, 4 Apr 2007 11:36:24 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, ego@...ibm.com,
	paulmck@...ibm.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, vatsa@...ibm.com,
	Oleg Nesterov <oleg@...sign.ru>, dipankar@...ibm.com,
	dino@...ibm.com, masami.hiramatsu.pt@...achi.com,
	Roland McGrath <roland@...hat.com>
Subject: Re: utrace merge

On Wed, Apr 04, 2007 at 12:06:44PM +0200, Ingo Molnar wrote:
> 
> * Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > urgh, I screwed up, sorry.
> > 
> > utrace-prep-2 reverts a bit of the underlying tree so that the utrace 
> > patches (which are against mainline) don't throw a tremendous reject 
> > which has to be fixed each time I pull Roland's tree.  I'm supposed to 
> > reapply that change after the utrace patches but forgot.
> 
> btw., how about pushing utrace to v2.6.22, is anything big holding that 
> up? (other than Roland's modesty, which we should gently but firmly 
> ignore in this case =B-)

a) lots of architecture support
b) lots of overengineered and obsfucated code
c) missing public information

I've also not gotten any feedback to my ages old review and the issues
don't seem to be addressed either.



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