a5648b8094
chase_symlinks() would return negative on error, and either a non-negative status or a non-negative fd when CHASE_OPEN was given. This made the interface quite complicated, because dependning on the flags used, we would get two different "types" of return object. Coverity was always confused by this, and flagged every use of chase_symlinks() without CHASE_OPEN as a resource leak (because it would this that an fd is returned). This patch uses a saparate output parameter, so there is no confusion. (I think it is OK to have functions which return either an error or an fd. It's only returning *either* an fd or a non-fd that is confusing.) |
||
|---|---|---|
| .. | ||
| sd-bus | ||
| sd-daemon | ||
| sd-device | ||
| sd-event | ||
| sd-hwdb | ||
| sd-id128 | ||
| sd-login | ||
| sd-netlink | ||
| sd-network | ||
| sd-path | ||
| sd-resolve | ||
| sd-utf8 | ||
| disable-mempool.c | ||
| libsystemd.pc.in | ||
| libsystemd.sym | ||
| meson.build | ||