Re: [PATCH 7/8] refs: stop setting EINVAL and ELOOP in symref resolution
From: Jonathan Tan <hidden>
Date: 2021-06-03 02:56:13
quoted hunk ↗ jump to hunk
From: Han-Wen Nienhuys <redacted> The only caller of refs_resolve_ref_unsafe_with_errno() is in refs/files-backend.c, and it only cares about EISDIR and ENOTDIR. Signed-off-by: Han-Wen Nienhuys <redacted> --- refs.c | 3 --- 1 file changed, 3 deletions(-)diff --git a/refs.c b/refs.c index 6e746cb01f24..597e4d1f18f9 100644 --- a/refs.c +++ b/refs.c@@ -1706,7 +1706,6 @@ static const char *refs_resolve_ref_unsafe_errno(struct ref_store *refs, if (check_refname_format(refname, REFNAME_ALLOW_ONELEVEL)) { if (!(resolve_flags & RESOLVE_REF_ALLOW_BAD_NAME) || !refname_is_safe(refname)) { - errno = EINVAL; return NULL; }
I don't think this is related to avoiding errno and conveying error information through an out param. But besides that, as it is, I'm not sure that this is correct. Even if EINVAL is not checked by the caller, setting errno to EINVAL here means avoiding exposing a potential EISDIR/ENOTDIR that a preceding call set. Same comment for the other instances.