On 01/30/2014 09:57 AM, Andy Lutomirski wrote:
>
> By definition there aren't any broken users of the new functions,
> because there aren't any users at all. So... should we start
> randomizing this thing from the beginning?
>
The vdso already exists. It isn't new. Randomizing it might be a good
idea, though; it already is randomized on 64 bits.
> Also, since the VVAR page has a real vma, should something be done to
> prevent mprotect or ptrace from COWing it? Users will be rather
> surprised if it suddenly stops updating.
What happens currently on 64 bits? I think we just take the attitude
that "don't do that, then", and it hasn't seemed to be a problem.
> Finally, this might be the time to kill off the userspace mapping of
> the HPET. I suspect that there are few if any machines for which the
> HPET is fast enough that avoiding a syscall matters at all. (On my
> box at work, reading the HPET takes ~500 nanoseconds. I can do a lot
> of syscalls in that amount of time.)
I think this can be independent of extending the current 64-bit
functionality to 32 bits. It is a valid question, though.
-hpa
--
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/
