qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Murilo Opsfelder Araujo <muriloo@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, qemu-ppc@nongnu.org,
	Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Eric Blake <eblake@redhat.com>,
	R Nageswara Sastry <nasastry@in.ibm.com>,
	Murilo Opsfelder Araujo <muriloo@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 0/1] qemu/nbd: fix segmentation fault when .desc is not null-terminated
Date: Fri,  5 Jan 2018 11:32:40 -0200	[thread overview]
Message-ID: <20180105133241.14141-1-muriloo@linux.vnet.ibm.com> (raw)

Hello, QEMU community.

The following patch is to fix a segmentation fault when nbd_runtime_opts.desc is
not null-terminated.

This issue emerged when building QEMU with --enable-gcov, as described by
https://bugs.launchpad.net/qemu/+bug/1727259.

To reproduce on ppc64le, run the following commands on QEMU git tree:

mkdir build
mkdir -p tests/qemu-iotests/scratch
cd build
../configure --target-list=ppc64-softmmu --enable-gcov
make -j$(nproc)

./qemu-img create -f qcow2 -o compat=1.1 ./tests/qemu-iotests/scratch/t.qcow2 64M
./qemu-io --cache writeback -f qcow2 -c "write -P 0xa 0x1000 0x1000" ./tests/qemu-iotests/scratch/t.qcow2
./qemu-io --cache writeback -f qcow2 -c "write -P 0xb 0x2000 0x1000" ./tests/qemu-iotests/scratch/t.qcow2
./qemu-img snapshot -c sn1 ./tests/qemu-iotests/scratch/t.qcow2
./qemu-io --cache writeback -f qcow2 -c "write -P 0xc 0x1000 0x1000" ./tests/qemu-iotests/scratch/t.qcow2
./qemu-io --cache writeback -f qcow2 -c "write -P 0xd 0x2000 0x1000" ./tests/qemu-iotests/scratch/t.qcow2
./qemu-img check -f qcow2 ./tests/qemu-iotests/scratch/t.qcow2
./qemu-io --cache writeback -f qcow2 -c "read -P 0xc 0x1000 0x1000" ./tests/qemu-iotests/scratch/t.qcow2
./qemu-io --cache writeback -f qcow2 -c "read -P 0xd 0x2000 0x1000" ./tests/qemu-iotests/scratch/t.qcow2

# run in background, wait some seconds until it starts
./qemu-nbd -v -t -k ${PWD}/tests/qemu-iotests/scratch/test_qemu_nbd_socket ./tests/qemu-iotests/scratch/t.qcow2 -l sn1 &
sleep 5

# this will cause qemu-io to segfault
./qemu-io --cache writeback -f qcow2 -f raw --cache=writeback -r -c "read -P 0xa 0x1000 0x1000" nbd:unix:${PWD}/tests/qemu-iotests/scratch/test_qemu_nbd_socket

# kill qemu-nbd
kill $(pidof qemu-nbd)

Cheers
Murilo

Murilo Opsfelder Araujo (1):
  block/nbd: fix segmentation fault when .desc is not null-terminated

 block/nbd.c | 1 +
 1 file changed, 1 insertion(+)

-- 
2.14.3

             reply	other threads:[~2018-01-05 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 13:32 Murilo Opsfelder Araujo [this message]
2018-01-05 13:32 ` [Qemu-devel] [PATCH 1/1] block/nbd: fix segmentation fault when .desc is not null-terminated Murilo Opsfelder Araujo
2018-01-05 13:57   ` Eric Blake
2018-01-05 14:47     ` Murilo Opsfelder Araújo
2018-01-05 17:08       ` Eric Blake

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=20180105133241.14141-1-muriloo@linux.vnet.ibm.com \
    --to=muriloo@linux.vnet.ibm.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=nasastry@in.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).