Theodore Ts'o wrote: > > ... proposed a hack where mlockall() would adjust RLIMIT_MEMLOCK. > Yes, no question it's a hack and a special case; the question is > whether cure or the disease is worse. What about exec? The memory locks are removed on exec but with that hack the raised limit would stay. Looks like a security bug. Ciao, ET. - 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: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- References:
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: "Theodore Ts'o" <[email protected]>
- Re: Rationale for RLIMIT_MEMLOCK?
- Prev by Date: Re: [PATCH] Export symbols so CONFIG_INPUT works as a module
- Next by Date: Re: e100 oops on resume
- Previous by thread: Re: Rationale for RLIMIT_MEMLOCK?
- Next by thread: Re: Rationale for RLIMIT_MEMLOCK?
- Index(es):
 |