|| ||Roland McGrath <roland-AT-redhat.com> |
|| ||Oleg Nesterov <oleg-AT-redhat.com> |
|| ||Re: [RFC,PATCH 0/14] utrace/ptrace |
|| ||Tue, 1 Dec 2009 16:46:43 -0800 (PST)|
|| ||Peter Zijlstra <peterz-AT-infradead.org>, linux-kernel-AT-vger.kernel.org,
Christoph Hellwig <hch-AT-infradead.org>,
"Frank Ch. Eigler" <fche-AT-redhat.com>, utrace-devel-AT-redhat.com,
Alexey Dobriyan <adobriyan-AT-gmail.com>|
|| ||Article, Thread
Note to all: I'm on the road this week (having had a holiday last week)
and will be somewhat slow in replying on these threads, but I will be
sure to get to them all.
> Yes, nobody likes 2 implementations. I guess Roland and me hate
> CONFIG_UTRACE much more than anybody else.
:-) We both hate maintaining the old ptrace implementation, that is true!
The other thing we hate is having our work delayed arbitrarily again and
again to wait for the arch maintainers of arch's we don't use ourselves.
Oleg and I have been trying to follow the advice we get on how to get this
work merged in. When multiple gate-keepers give conflicting advice, we
really don't know what to do next. Our interest is in whatever path
smooths the merging of our work. We'd greatly prefer to spend our time
hacking on our new code to make it better or different in cool and useful
ways than to spend more time guessing what order of patches and rejuggling
of the work will fit the changing whims of the next round of review.
We don't want to rush anyone, like uninterested arch maintainers. We don't
want to break anyone who doesn't care about our work (we do test for ptrace
regressions but of course new code will always have new bugs so some
instances of instability in the transition to a new ptrace implementation
have to be expected no matter how hard we try). We just don't want to keep
working out of tree.
The advantage of making the new code optional is, obviously, that you can
turn it off. That is, lagging arch's won't be broken, just unable to turn
it on. And, anyone who doesn't want to try anything new yet can just turn
it off and not be exposed to new code.
The advantage of making the new code nonoptional is, obviously, that you
can't turn it off. The old implementation will be gone and we won't have
to maintain it any more (outside some -stable streams for a while). The
kernel source will be cleaner with no optional old cruft code duplicating
functionality. All ptrace users will be testing the new code, and so we'll
find its bugs and gain confidence that it works solidly.
Like I've said, we want to do whatever the people want. My concern about
what Christoph has suggested is that it really seems like an open-ended
delay depending on some arch people who are not even in the conversation.
For anyone either who likes utrace or who is concerned about its details,
the sooner we are working in-tree the sooner we can really hash it out
thoroughly and get to having merged code that works well. As long as there
is anything unfinished like arch work that we've decided is a gating event,
then the review and hashing out of the new code itself does not seem to get
very serious. (To wit, this thread is still talking about merge order and
such, another long thread was about incidental trivia, and we've only just
started to see a tiny bit of actual code review today.)
to post comments)