From: Zhao Liu <zhao1....@intel.com> The error_vprepend() should use ERRP_GUARD() just as the documentation of ERRP_GUARD() says:
> It must be used when the function dereferences @errp or passes > @errp to error_prepend(), error_vprepend(), or error_append_hint(). Considering that error_vprepend() is also an API provided in error.h, it is necessary to add it to the description of the rules for using ERRP_GUARD(). Cc: Markus Armbruster <arm...@redhat.com> Cc: Michael Roth <michael.r...@amd.com> Signed-off-by: Zhao Liu <zhao1....@intel.com> Reviewed-by: Markus Armbruster <arm...@redhat.com> Message-ID: <20240311033822.3142585-2-zhao1....@linux.intel.com> Signed-off-by: Thomas Huth <th...@redhat.com> --- include/qapi/error.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/qapi/error.h b/include/qapi/error.h index f21a231bb1..71f8fb2c50 100644 --- a/include/qapi/error.h +++ b/include/qapi/error.h @@ -207,7 +207,7 @@ * * Without ERRP_GUARD(), use of the @errp parameter is restricted: * - It must not be dereferenced, because it may be null. - * - It should not be passed to error_prepend() or + * - It should not be passed to error_prepend(), error_vprepend(), or * error_append_hint(), because that doesn't work with &error_fatal. * ERRP_GUARD() lifts these restrictions. * -- 2.44.0
