qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2] file-posix: Use error API properly


From: Eric Blake
Subject: Re: [Qemu-devel] [PATCH v2] file-posix: Use error API properly
Date: Wed, 31 Oct 2018 09:57:25 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1

On 10/31/18 12:39 AM, Fam Zheng wrote:
Use error_report for situations that affect user operation (i.e.  we're
actually returning error), and warn_report/warn_report_err when some
less critical error happened but the user operation can still carry on.

For raw_normalize_devicepath, add Error parameter to propagate to
its callers.

Suggested-by: Markus Armbruster <address@hidden>
Signed-off-by: Fam Zheng <address@hidden>


@@ -214,8 +214,7 @@ static int raw_normalize_devicepath(const char **filename)
      fname = *filename;
      dp = strrchr(fname, '/');
      if (lstat(fname, &sb) < 0) {
-        fprintf(stderr, "%s: stat failed: %s\n",
-            fname, strerror(errno));
+        error_setg(errp, "%s: stat failed: %s", fname, strerror(errno));
          return -errno;

error_setg_errno() is nicer here. In fact, should we have a Coverity script that looks for error_setg(... strerror())?

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]