2019-03-07 17:58:38 +03:00
|
|
|
#!/usr/bin/env bash
|
2021-01-16 16:44:19 +03:00
|
|
|
# group: rw auto quick
|
2016-01-29 18:36:02 +03:00
|
|
|
#
|
2016-02-18 23:37:33 +03:00
|
|
|
# Test case for ejecting a BlockBackend with an NBD server attached to it
|
|
|
|
#
|
|
|
|
# Verify that the NBD server stops offering the drive when ejecting a
|
|
|
|
# BlockDriverState tree from a BlockBackend (that is, a medium from a
|
|
|
|
# drive) exposed via an NBD server.
|
2016-01-29 18:36:02 +03:00
|
|
|
#
|
|
|
|
# Copyright (C) 2016 Red Hat, Inc.
|
|
|
|
#
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
|
|
# it under the terms of the GNU General Public License as published by
|
|
|
|
# the Free Software Foundation; either version 2 of the License, or
|
|
|
|
# (at your option) any later version.
|
|
|
|
#
|
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
# GNU General Public License for more details.
|
|
|
|
#
|
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
#
|
|
|
|
|
|
|
|
# creator
|
2022-03-22 20:42:12 +03:00
|
|
|
owner=hreitz@redhat.com
|
2016-01-29 18:36:02 +03:00
|
|
|
|
|
|
|
seq="$(basename $0)"
|
|
|
|
echo "QA output created by $seq"
|
|
|
|
|
|
|
|
status=1 # failure is the default!
|
|
|
|
|
|
|
|
_cleanup()
|
|
|
|
{
|
2017-04-18 22:42:41 +03:00
|
|
|
_cleanup_qemu
|
2016-01-29 18:36:02 +03:00
|
|
|
_cleanup_test_img
|
2019-10-17 16:31:39 +03:00
|
|
|
rm -f "$SOCK_DIR/nbd"
|
2016-01-29 18:36:02 +03:00
|
|
|
}
|
|
|
|
trap "_cleanup; exit \$status" 0 1 2 3 15
|
|
|
|
|
|
|
|
# get standard environment, filters and checks
|
|
|
|
. ./common.rc
|
|
|
|
. ./common.filter
|
|
|
|
. ./common.qemu
|
|
|
|
|
|
|
|
_supported_fmt generic
|
2020-10-27 22:05:59 +03:00
|
|
|
_supported_proto file fuse
|
2016-01-29 18:36:02 +03:00
|
|
|
_supported_os Linux
|
|
|
|
|
|
|
|
_make_test_img 64k
|
|
|
|
|
|
|
|
$QEMU_IO -c 'write -P 42 0 64k' "$TEST_IMG" | _filter_qemu_io
|
|
|
|
|
2017-06-26 15:35:07 +03:00
|
|
|
if test "$IMGOPTSSYNTAX" = "true"
|
|
|
|
then
|
|
|
|
SYSEMU_DRIVE_ARG=if=none,media=cdrom,id=drv,"$TEST_IMG"
|
|
|
|
else
|
|
|
|
SYSEMU_DRIVE_ARG=if=none,media=cdrom,id=drv,file="$TEST_IMG",driver=$IMGFMT
|
|
|
|
fi
|
|
|
|
|
2016-01-29 18:36:02 +03:00
|
|
|
keep_stderr=y \
|
2017-06-26 15:35:07 +03:00
|
|
|
_launch_qemu -drive $SYSEMU_DRIVE_ARG \
|
2016-01-29 18:36:02 +03:00
|
|
|
2> >(_filter_nbd)
|
|
|
|
|
|
|
|
_send_qemu_cmd $QEMU_HANDLE \
|
|
|
|
"{ 'execute': 'qmp_capabilities' }" \
|
|
|
|
'return'
|
|
|
|
|
|
|
|
_send_qemu_cmd $QEMU_HANDLE \
|
|
|
|
"{ 'execute': 'nbd-server-start',
|
|
|
|
'arguments': { 'addr': { 'type': 'unix',
|
2019-10-17 16:31:39 +03:00
|
|
|
'data': { 'path': '$SOCK_DIR/nbd' }}}}" \
|
2016-01-29 18:36:02 +03:00
|
|
|
'return'
|
|
|
|
|
|
|
|
_send_qemu_cmd $QEMU_HANDLE \
|
|
|
|
"{ 'execute': 'nbd-server-add',
|
|
|
|
'arguments': { 'device': 'drv' }}" \
|
|
|
|
'return'
|
|
|
|
|
nbd-client: Refuse read-only client with BDRV_O_RDWR
The NBD spec says that clients should not try to write/trim to
an export advertised as read-only by the server. But we failed
to check that, and would allow the block layer to use NBD with
BDRV_O_RDWR even when the server is read-only, which meant we
were depending on the server sending a proper EPERM failure for
various commands, and also exposes a leaky abstraction: using
qemu-io in read-write mode would succeed on 'w -z 0 0' because
of local short-circuiting logic, but 'w 0 0' would send a
request over the wire (where it then depends on the server, and
fails at least for qemu-nbd but might pass for other NBD
implementations).
With this patch, a client MUST request read-only mode to access
a server that is doing a read-only export, or else it will get
a message like:
can't open device nbd://localhost:10809/foo: request for write access conflicts with read-only export
It is no longer possible to even attempt writes over the wire
(including the corner case of 0-length writes), because the block
layer enforces the explicit read-only request; this matches the
behavior of qcow2 when backed by a read-only POSIX file.
Fix several iotests to comply with the new behavior (since
qemu-nbd of an internal snapshot, as well as nbd-server-add over QMP,
default to a read-only export, we must tell blockdev-add/qemu-io to
set up a read-only client).
CC: qemu-stable@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20171108215703.9295-3-eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
2017-11-09 00:56:58 +03:00
|
|
|
$QEMU_IO_PROG -f raw -r -c 'read -P 42 0 64k' \
|
2019-10-17 16:31:39 +03:00
|
|
|
"nbd+unix:///drv?socket=$SOCK_DIR/nbd" 2>&1 \
|
2016-01-29 18:36:02 +03:00
|
|
|
| _filter_qemu_io | _filter_nbd
|
|
|
|
|
2020-09-24 18:27:07 +03:00
|
|
|
# The order of 'return' and the BLOCK_EXPORT_DELETED event is undefined. Just
|
|
|
|
# wait until we've twice seen one of them. Filter the 'return' line out so that
|
|
|
|
# the output is defined.
|
2016-01-29 18:36:02 +03:00
|
|
|
_send_qemu_cmd $QEMU_HANDLE \
|
|
|
|
"{ 'execute': 'eject',
|
|
|
|
'arguments': { 'device': 'drv' }}" \
|
2020-09-24 18:27:07 +03:00
|
|
|
'return\|BLOCK_EXPORT_DELETED' |
|
|
|
|
grep -v 'return'
|
|
|
|
|
|
|
|
_send_qemu_cmd $QEMU_HANDLE '' 'return\|BLOCK_EXPORT_DELETED' |
|
|
|
|
grep -v 'return'
|
2016-01-29 18:36:02 +03:00
|
|
|
|
nbd-client: Refuse read-only client with BDRV_O_RDWR
The NBD spec says that clients should not try to write/trim to
an export advertised as read-only by the server. But we failed
to check that, and would allow the block layer to use NBD with
BDRV_O_RDWR even when the server is read-only, which meant we
were depending on the server sending a proper EPERM failure for
various commands, and also exposes a leaky abstraction: using
qemu-io in read-write mode would succeed on 'w -z 0 0' because
of local short-circuiting logic, but 'w 0 0' would send a
request over the wire (where it then depends on the server, and
fails at least for qemu-nbd but might pass for other NBD
implementations).
With this patch, a client MUST request read-only mode to access
a server that is doing a read-only export, or else it will get
a message like:
can't open device nbd://localhost:10809/foo: request for write access conflicts with read-only export
It is no longer possible to even attempt writes over the wire
(including the corner case of 0-length writes), because the block
layer enforces the explicit read-only request; this matches the
behavior of qcow2 when backed by a read-only POSIX file.
Fix several iotests to comply with the new behavior (since
qemu-nbd of an internal snapshot, as well as nbd-server-add over QMP,
default to a read-only export, we must tell blockdev-add/qemu-io to
set up a read-only client).
CC: qemu-stable@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20171108215703.9295-3-eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
2017-11-09 00:56:58 +03:00
|
|
|
$QEMU_IO_PROG -f raw -r -c close \
|
2019-10-17 16:31:39 +03:00
|
|
|
"nbd+unix:///drv?socket=$SOCK_DIR/nbd" 2>&1 \
|
2016-01-29 18:36:02 +03:00
|
|
|
| _filter_qemu_io | _filter_nbd
|
|
|
|
|
|
|
|
_send_qemu_cmd $QEMU_HANDLE \
|
|
|
|
"{ 'execute': 'quit' }" \
|
|
|
|
'return'
|
|
|
|
|
|
|
|
wait=1 _cleanup_qemu
|
|
|
|
|
|
|
|
# success, all done
|
|
|
|
echo '*** done'
|
|
|
|
rm -f $seq.full
|
|
|
|
status=0
|