* Andy Lutomirski <l...@amacapital.net> wrote:
> > OK.
> > I'll try to test the patch tomorrow, but I think the sigreturn()'s
> > capability detection is still needed to easily replace the iret trampoline
> > in userspace (without generating a signal and testing by hands).
> > Can of course be done with a run-time kernel version check...
>
> That feature is so specialized that I think you should just probe it.
>
> void foo(...) {
> sigcontext->ss = 7;
> }
>
> modify_ldt(initialize descriptor 0);
> sigaction(SIGUSR1, foo, SA_SIGINFO);
> if (ss == 7)
> yay;
>
> Fortunately, all kernels that restore ss also have espfix64, so you
> don't need to worry about esp[31:16] corruption on those kernels
> either.
>
> I suppose we could add a new uc_flag to indicate that ss is saved and
> restored,
> though. Ingo, hpa: any thoughts on that? There will always be some kernel
> versions that save and restore ss but don't set the flag, though.
So this new flag would essentially be a 'the ss save/restore bug is fixed for
sure' flag, not covering old kernels that happen to have the correct behavior,
right?
Could you please map out the range of kernel versions involved - which ones:
- 'never do the right thing'
- 'do the right thing sometimes'
- 'do the right thing always, but by accident'
- 'do the right thing always and intentionally'
?
I'd hate to complicate a legacy ABI any more. My gut feeling is to let apps
either
assume that the kernel works right, or probe the actual behavior. Adding the
flag
just makes it easy to screw certain kernel versions that would still work fine
if
the app used actual probing. So I don't see the flag as an improvement.
If your patch fixes the regression that would be a good first step.
Please also send the fix in email instead of just pointing to a Git tree, so
that
people can comment on it.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
