search for: almost4k

...| fail=1 -# FIXME: Right now, we can't accept full 4k length - this should succeed + nbd+unix:///'$name4k'\?socket=$unixsocket' || fail=1 +# See above comment about whether this is testing nbdkit or qemu: nbdkit -U - null --run 'qemu-io -r -f raw -c quit \ - nbd+unix:///'$almost4k'\?socket=$unixsocket' && fail=1 + nbd+unix:///'a$name4k'\?socket=$unixsocket' && fail=1 # The rest of this test uses the ‘qemu-nbd --list’ option added in qemu 4.0. if ! qemu-nbd --help | grep -sq -- --list; then @@ -96,8 +96,6 @@ if ! qemu-nbd --help | grep...

Since the v1 series (0/4, at [1]), I've applied patches 1 and 2, rewritten patch 3 [Forbid NUL in export and context names] into patch 4 here, patch 4 there turned into patch 6 here, and everything else here is new. [1]https://www.redhat.com/archives/libguestfs/2019-September/msg00180.html I don't know if there is a handy reusable function for checking whether a string contains valid

...19 Red Hat Inc. +# Copyright (C) 2019-2020 Red Hat Inc. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are @@ -53,10 +53,6 @@ name1k=$name256$name256$name256$name256 name4k=$name1k$name1k$name1k$name1k almost4k=${name4k%8$name16} -# Test behavior of -e: accept 4k max, reject longer -nbdkit -U - -e $name4k null --run true || fail=1 -nbdkit -U - -e a$name4k null --run true && fail=1 - # Test that $exportname and $uri reflect the name out=$(nbdkit -U - -e $name4k null --run 'echo $exportname...