From: Markus Armbruster <armbru@redhat.com>
To: Xie Yongji <xieyongji@bytedance.com>
Cc: kwolf@redhat.com, stefanha@redhat.com, armbru@redhat.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/4] libvduse: Pass positive value to strerror()
Date: Wed, 29 Jun 2022 11:38:49 +0200 [thread overview]
Message-ID: <877d4zq05y.fsf@pond.sub.org> (raw)
In-Reply-To: <20220627090203.87-4-xieyongji@bytedance.com> (Xie Yongji's message of "Mon, 27 Jun 2022 17:02:02 +0800")
Xie Yongji <xieyongji@bytedance.com> writes:
> The value passed to strerror() should be positive.
> So let's fix it.
>
> Fixes: Coverity CID 1490226, 1490223
> Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2022-06-29 9:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:01 [PATCH 0/4] Fix some coverity issues on VDUSE Xie Yongji
2022-06-27 9:02 ` [PATCH 1/4] libvduse: Fix the incorrect function name Xie Yongji
2022-06-29 9:37 ` Markus Armbruster
2022-06-27 9:02 ` [PATCH 2/4] libvduse: Replace strcpy() with strncpy() Xie Yongji
2022-06-28 0:25 ` Richard Henderson
2022-06-28 2:59 ` Yongji Xie
2022-06-29 9:38 ` Markus Armbruster
2022-06-27 9:02 ` [PATCH 3/4] libvduse: Pass positive value to strerror() Xie Yongji
2022-06-28 0:26 ` Richard Henderson
2022-06-29 9:38 ` Markus Armbruster [this message]
2022-06-27 9:02 ` [PATCH 4/4] libvduse: Check the return value of some ioctls Xie Yongji
2022-06-29 9:41 ` Markus Armbruster
2022-06-29 11:10 ` Yongji Xie
2022-06-29 11:39 ` Markus Armbruster
2022-06-29 12:37 ` Yongji Xie
2022-06-29 13:22 ` Markus Armbruster
2022-06-29 13:28 ` Yongji Xie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d4zq05y.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xieyongji@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).