Arjan van de Ven <[email protected]> writes: > (all others default to executable stack) Except ia64. Andreas. -- Andreas Schwab, SuSE Labs, [email protected] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - 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/
- Follow-Ups:
- Re: how to determine if the noexec stack is defined by an application
- From: Arjan van de Ven <[email protected]>
- Re: how to determine if the noexec stack is defined by an application
- References:
- how to determine if the noexec stack is defined by an application
- From: Florin Andrei <[email protected]>
- Re: how to determine if the noexec stack is defined by an application
- From: Arjan van de Ven <[email protected]>
- Re: how to determine if the noexec stack is defined by an application
- From: Andreas Schwab <[email protected]>
- Re: how to determine if the noexec stack is defined by an application
- From: Arjan van de Ven <[email protected]>
- how to determine if the noexec stack is defined by an application
- Prev by Date: Re: [PATCH] Optional Beeping During Resume From Suspend To Ram.
- Next by Date: [PATCH] move suspend includes into right place (was Re: suspend2 merge (was Re: [Suspend2-devel] Re: CFS and suspend2: hang in atomic copy))
- Previous by thread: Re: how to determine if the noexec stack is defined by an application
- Next by thread: Re: how to determine if the noexec stack is defined by an application
- Index(es):