Hello,
>
> The location of the vsyscall page is different on 32 and 64 bit
> machines. So 0xffffe000 is NOT the address you are looking for while
> dealing with the 64 bit machine. Rather 0xffffffffff600000 is the
> correct location (on x86-64).
>
Both my process's are 32-bit process's, its just one runs on 64-bit
machine and other runs on 32-bit machine. The write from address
0xffffe0000 to a file on a 32-bit machine fails, but does'nt fail on
64-bit machine (the process is still 32-bit although it runs on
64-bit).
How can the virtual address of 0xffffffffff600000 exist in a 32-bit
process ? (May be I have not made myself clear in explaining the
problem?? :-?)
Best,
Vamsi.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |