* Zachary Amsden ([email protected]) wrote:
> >+ DEFINE(VSYSCALL_BASE, (PAGE_OFFSET - 2*PAGE_SIZE));
>
> Ok, I'm confused. What fixed math?
Sorry, bad choice of words. From above, the VYSYCALL_BASE is known
at compile time (in asm-offsets.h). So the SYSENTER_RETURN is still
fixed addr. For execshield it's truly dynamic, so you get something
like this instead of the constant SYSENTER_RETURN:
- pushl $SYSENTER_RETURN
+ pushl (TI_sysenter_return-THREAD_SIZE+8+4*4)(%esp)
thanks,
-chris
-
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/
- References:
- [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
- Re: [RFC, PATCH 7/24] i386 Vmi memory hole
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]