Messages in this thread | | | Subject | Re: Rationale for RLIMIT_MEMLOCK? | From | Arjan van de Ven <> | Date | Mon, 23 Jan 2006 20:04:36 +0100 |
| |
On Mon, 2006-01-23 at 19:55 +0100, Matthias Andree wrote: > On Mon, 23 Jan 2006, Arjan van de Ven wrote: > > > hmm... curious that mlockall() succeeds with only a 32kb rlimit.... > > It's quite obvious with the seteuid() shuffling behind the scenes of the > app, for the mlockall() runs with euid==0, and the later mmap() with euid!=0.
hmm how on earth was that supposed to work at all????
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |