Zitat von Linus Torvalds <[email protected]>:
On Mon, Mar 10, 2014 at 2:25 PM, <[email protected]> wrote:
This was discovered by me.
Sorry for the misattribution.
But this is not a real solution, at least when vcpu function support
will be added, then the code size will exceed the page size. Reserving
two pages for the VDSO is a good option.
Quite frankly, there is no way in hell I will take a patch like that
for 3.14 any more, and I would argue against it for stable.
Now, if this problem never happens with current kernels (because it's
purely due to the patch in -tip), then I don't much care.
That said, I don't understand why we are even adding new features like
this to 32-bit mode in the first place, so if that patch is the sole
source of all this headache, then why not just throw the patch away?
The patch is working. And for this current issue there is a solution i already
announced.
A dual VDSO: a one page sized VDSO for the compat mode which has only
the syscall
code and on multi page sized VDSO which is mapped into user space for
the non compat
mode.
This will work and has no side effects.
- Stefani
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
