Arjan van de Ven wrote:
>> Why not show both.
>> "intent" and "effective".
>
> that would change the file format .. which is used by apps today already
> (including glibc)
So, what about having another file, say /proc/self/emaps (effective
maps) that would display how things are really set.
Arjan van de Ven wrote:
On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory
On Thu, 2006-12-14 at 13:07 +0100, Franck Pommereau wrote:
> >> # grep maps /proc/self/maps
> >> bfce8000-bfcfe000 rw-p bfce8000 00:00 0 [stack]
> >
> > this shows that the *intent* is to have it non-executable.
> > Not all x86 processors can enforce this. All modern ones do.
>
> Mine
>> # grep maps /proc/self/maps
>> bfce8000-bfcfe000 rw-p bfce8000 00:00 0 [stack]
>
> this shows that the *intent* is to have it non-executable.
> Not all x86 processors can enforce this. All modern ones do.
Mine is quite recent:
# cat /proc/cpuinfo
processor : 0
vendor_id
On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
> Dear Linux developers,
>
> I recently discovered that the Linux kernel on 32 bits x86 processors
> reports the stack as being non-executable while it is actually
> executable (because located in the same memory segment).
this is not
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory segment).
# grep maps /proc/self/maps
bfce8000-bfcfe000 rw-p bfce8000 00:00 0
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory segment).
# grep maps /proc/self/maps
bfce8000-bfcfe000 rw-p bfce8000 00:00 0
On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory segment).
this is not per se
# grep maps /proc/self/maps
bfce8000-bfcfe000 rw-p bfce8000 00:00 0 [stack]
this shows that the *intent* is to have it non-executable.
Not all x86 processors can enforce this. All modern ones do.
Mine is quite recent:
# cat /proc/cpuinfo
processor : 0
vendor_id :
On Thu, 2006-12-14 at 13:07 +0100, Franck Pommereau wrote:
# grep maps /proc/self/maps
bfce8000-bfcfe000 rw-p bfce8000 00:00 0 [stack]
this shows that the *intent* is to have it non-executable.
Not all x86 processors can enforce this. All modern ones do.
Mine is quite
Arjan van de Ven wrote:
On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory
Arjan van de Ven wrote:
Why not show both.
intent and effective.
that would change the file format .. which is used by apps today already
(including glibc)
So, what about having another file, say /proc/self/emaps (effective
maps) that would display how things are really set.
Currently, is
12 matches
Mail list logo
