bpf: Correctly propagate errors up from bpf_core_composites_match

This change addresses a comment made earlier [0] about a missing return
of an error when __bpf_core_types_match is invoked from
bpf_core_composites_match, which could have let to us erroneously
ignoring errors.

Regarding the typedef name check pointed out in the same context, it is
not actually an issue, because callers of the function perform a name
check for the root type anyway. To make that more obvious, let's add
comments to the function (similar to what we have for
bpf_core_types_are_compat, which is called in pretty much the same
context).

[0]: https://lore.kernel.org/bpf/[e-mail]/T/#m55141e8f8cfd2e8d97e65328fa04852870d01af6

Suggested-by: Andrii Nakryiko <[e-mail]>
Signed-off-by: Daniel Müller <[e-mail]>
Signed-off-by: Andrii Nakryiko <[e-mail]>
Link: https://lore.kernel.org/bpf/[e-mail]

tools/lib/bpf/relo_core.c

···
 
 			err = __bpf_core_types_match(local_btf, local_m->type, targ_btf,
 						     targ_m->type, behind_ptr, level - 1);
+			if (err < 0)
+				return err;
 			if (err > 0) {
 				matched = true;
 				break;
···
 	return 1;
 }
 
-/* Check that two types "match".
+/* Check that two types "match". This function assumes that root types were
+ * already checked for name match.
  *
  * The matching relation is defined as follows:
  * - modifiers and typedefs are stripped (and, hence, effectively ignored)
···
 	if (!local_t || !targ_t)
 		return -EINVAL;
 
+	/* While the name check happens after typedefs are skipped, root-level
+	 * typedefs would still be name-matched as that's the contract with
+	 * callers.
+	 */
 	if (!bpf_core_names_match(local_btf, local_t->name_off, targ_btf, targ_t->name_off))
 		return 0;