From: Jagannathan Raman <jag.raman@oracle.com>
To: berrange@redhat.com
Cc: elena.ufimtseva@oracle.com, stefanha@gmail.com, qemu-devel@nongnu.org
Subject: [PATCH] Fix segfault during NBD iotest 083
Date: Fri, 12 Feb 2021 06:16:06 -0500 [thread overview]
Message-ID: <cover.1613128220.git.jag.raman@oracle.com> (raw)
Hi,
The patch fixes a segfault issue. error_prepend() in
qio_channel_readv_full_all() sets a NULL *errp when
ret is 0.
We ran the following tests with this patch and they all passed:
- cd tests/qemu-iotests && ./check -nbd 083
- make check
- make check-iotests
- CI using Travis. We also kicked off gitlab CI, but didn't
hear anything back from the server
Jagannathan Raman (1):
io: error_prepend() in qio_channel_readv_full_all() causes segfault
io/channel.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--
1.8.3.1
next reply other threads:[~2021-02-12 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 11:16 Jagannathan Raman [this message]
2021-02-12 11:16 ` [PATCH] io: error_prepend() in qio_channel_readv_full_all() causes segfault Jagannathan Raman
2021-02-12 11:16 ` Daniel P. Berrangé
2021-02-12 11:41 ` Jag Raman
2021-02-12 13:08 ` Eric Blake
2021-02-12 13:13 ` Jag Raman
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=cover.1613128220.git.jag.raman@oracle.com \
--to=jag.raman@oracle.com \
--cc=berrange@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).