Arjan van de Ven wrote: > sounds like a good argument to get the setuid functions marked > __must_check in glibc... There are too many false positives. E.g., in a SUID binaries switching back from a non-root UID to root will not fail. Very common. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- From: Solar Designer <[email protected]>
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- From: Michael Buesch <[email protected]>
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- From: Arjan van de Ven <[email protected]>
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- References:
- [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- From: Solar Designer <[email protected]>
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- From: [email protected] (Alex Riesen)
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- From: Solar Designer <[email protected]>
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- From: Arjan van de Ven <[email protected]>
- [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- Prev by Date: Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- Next by Date: Re: [PATCH] getsockopt() early argument sanity checking
- Previous by thread: Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- Next by thread: Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
- Index(es):
 |