> It is unclear (to me) what are the consequences of this problem?  What
quoted text
> are the user-visible effects of the fix?

I don't know off hand of something that cares.  (I have a test case, but
it's just contrived for the purpose.)  Something like UML could use this to
approximate PTRACE_SYSEMU when it's not there.  But we would have heard
before now if UML cared about this particular behavior on x86_64.

quoted text
> IOW: is it a 2.6.25 thing and if so, why?

No hurry.  It's been broken forever (regression vs native 32-bit).
(OTOH, the fixes are quite safe.)


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