linux-kernel - Re: [RFC, PATCH 0/2] utrace/ptrace: simplify/cleanup ptrace attach

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:	Mon,  4 May 2009 18:12:44 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	oleg@...hat.com, jdike@...toit.com, utrace-devel@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC, PATCH 0/2] utrace/ptrace: simplify/cleanup ptrace attach

> Staging the utrace patch at end-of-series would make sense if utrace is
> not on track for a 2.6.31 merge.
> 
> And afaict, this is indeed the case - things seem to have gone a bit
> quiet on the utrace front lately.

I don't think that is really accurate.  There has been a lack of any
reviewer comments on the actual content of the utrace patch (aside from
Oleg's own), which is indeed quieter on that front than I had expected.

The comments we did get, e.g. from hch, were that a compelling user of the
API should go in, such as converting ptrace.  Oleg's current ptrace revamp
work will culminate in replacing its innards with utrace calls.  It's my
hope that all this work will be ready in time for 2.6.31.

The reason the utrace patch should appear later in the series is that the
bulk of the ptrace cleanup series (including all patches done so far) will
not depend on utrace at all and will be mergeable independent of the fate
of utrace or that of any later utrace-dependent ptrace patches.  We expect
the utrace patch will get more updates that we hash out in the course of
the ptrace work.  That being so, it makes more sense (to me) to plan to
replace it later before merge time rather than include the old patch
earlier in the series and have other patches (including ones unrelated to
it) need to do incremental updates relative to it.

Thanks,
Roland
--
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/