Re: [PATCH] cleanup ptrace stops and remove notify_parent

[Roland McGrath]

> Should we also clean up and improve those with user-visible change?
> Those should be thought as separate issue?

The first answer to give is to the second question: yes, this is a
separate subject from the implementation changes we are discussing right
now.  I don't really want to get into discussing a different interface at
the moment, because I have more than enough to do this week already.

It is certainly something I have considered.  Cleaning up ptrace for use
on multi-threaded processes was no fun at all.  Dan Jacobowitz and I have
talked about this before, and my tendency is the same he mentioned, to
start along the lines of the Solaris /proc interface.  (However, I would
not make Solaris compatibility a priority over implementation sanity.)
But like I said, not for this week!

An important step to a sane and clean implementation of whatever new
interface will be to clean up the machine-specific parts of the
implementation that are required.  If I am ever going to work on this
code again and not turn homicidal, it needs to take the form of a general
framework for special state examination/mutation requests machines
require uses common code to present these in whatever new interface and
compatibly for the ptrace requests that now exist.  More for not this week.

I'd be happy to discuss details of all this stuff with anyone interested
in helping make it happen.  But, you know, later.


Thanks,
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/