linux-kernel - Re: [PATCH 0/2] utrace

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: <20080903183746.GA16175@infradead.org>
Date:	Wed, 3 Sep 2008 14:37:46 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Roland McGrath <roland@...hat.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] utrace

On Wed, Sep 03, 2008 at 05:09:27AM -0700, Roland McGrath wrote:
> I have spent a lot of time keeping the patch series up to date,
> rebasing, etc.  This has sunk all the time that I'd like to have been
> spending working on higher-level pieces such as the ntrace idea.
> 
> (This will be much better now that all the tracehook work is in 2.6.27.
> I know you don't buy the rationale I've explained for that work.  But I
> am confident that having this in is a substantial and immediate boon to
> the ease and efficiency of getting more work done sooner in this area.)

Yes, now you've got all the lowlevel bits in that should have been
long time ago :)  And you don;t have to rebase it all the time if you
don't have time for it.  Keep developing ntrace on one major release and
then you can forward-port the whole bunch at once less frequently.

> At the same time, many of the people who have asked me about the state
> of the effort say things to the effect that they would like to try
> writing some features based on such an API once it's been merged in.

Then the people should help with the upstream process, post their bits
to lkml, help you with forward-porting, etc.

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