Hi Anton, On Sunday, 2. April 2006 00:29, you wrote: > Add a prctl to change a tasks endian. While we only have powerpc code to > implement this so far, it seems like something that warrants a generic > interface (like setting floating point mode bits). Most programmers (and thus programs) expect this to be a compile time decision. What are the reasons of allowing to change it so dynamic at all? What are the security implications of this? My naive guess is, that it might defeat range checking of values in user space code. What about limiting this to be called once per task or VM? This will prevent most abuse scenarios, I can think of. Regards Ingo Oeser
Attachment:
pgplycyyBEV8j.pgp
Description: PGP signature
- Follow-Ups:
- Re: [PATCH] Add prctl to change endian of a task
- From: Alan Cox <[email protected]>
- Re: [PATCH] Add prctl to change endian of a task
- References:
- [PATCH] Add prctl to change endian of a task
- From: Anton Blanchard <[email protected]>
- [PATCH] Add prctl to change endian of a task
- Prev by Date: Re: [PATCH 1/1] POWERPC: Fix ppc32 compile with gcc+SSP in 2.6.16
- Next by Date: Occasional APC Smart-UPS CS 500 USB UPS troubles
- Previous by thread: [PATCH] Add prctl to change endian of a task
- Next by thread: Re: [PATCH] Add prctl to change endian of a task
- Index(es):