| commit | 35f05b2e2ee59e077bf949057dc0959ddd6e5249 | |
| author | Max Reitz <mreitz@redhat.com> | |
| Wed, 2 Oct 2019 17:40:52 +0000 (2 19:40 +0200) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Thu, 10 Oct 2019 10:13:23 +0000 (10 12:13 +0200) | ||
| tree | 5374075ab3c680bedb9ba5e3bb42317cf56d910c | treesnapshot (tar.gz zip) |
| parent | da51e998f849fa7cd543e82d2301a9031fbe48e5 | commitdiff |
iotests/162: Fix for newer Linux 5.3+
Linux 5.3 has made 0.0.0.0/8 a working IPv4 subnet. As such, "42" is
now a valid host, and the connection to it will (hopefully) time out
over a long period rather than quickly return with EINVAL.
So let us use a negative integer for testing that NBD will not crash
when it receives integer hosts. This way, the connection will again
fail quickly and reliably.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20191002174052.5773-1-mreitz@redhat.com
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
Linux 5.3 has made 0.0.0.0/8 a working IPv4 subnet. As such, "42" is
now a valid host, and the connection to it will (hopefully) time out
over a long period rather than quickly return with EINVAL.
So let us use a negative integer for testing that NBD will not crash
when it receives integer hosts. This way, the connection will again
fail quickly and reliably.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20191002174052.5773-1-mreitz@redhat.com
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
| tests/qemu-iotests/162 | diffblobblamehistory | |
| tests/qemu-iotests/162.out | diffblobblamehistory |