From: "Denis V. Lunev" <den@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>,
Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, hreitz@redhat.com,
kwolf@redhat.com
Subject: Re: [PATCH] iotests/277: Use iotests.sock_dir for socket creation
Date: Wed, 24 Jan 2024 18:59:38 +0100 [thread overview]
Message-ID: <e513bffc-636e-4921-b87d-be67a52457f1@virtuozzo.com> (raw)
In-Reply-To: <3v7hvc2kt7obfhvnfrgmtwk4ofvy5dmrkiho3cbqsm2vnfhnl2@6n5i47olcp64>
On 1/24/24 18:43, Eric Blake wrote:
> On Wed, Jan 24, 2024 at 06:22:57PM +0200, Andrey Drobyshev wrote:
>> If socket path is too long (longer than 108 bytes), socket can't be
>> opened. This might lead to failure when test dir path is long enough.
>> Make sure socket is created in iotests.sock_dir to avoid such a case.
>>
>> This commit basically aligns iotests/277 with the rest of iotests.
>>
>> Signed-off-by: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
>> ---
>> tests/qemu-iotests/277 | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
>> diff --git a/tests/qemu-iotests/277 b/tests/qemu-iotests/277
>> index 24833e7eb6..4224202ac2 100755
>> --- a/tests/qemu-iotests/277
>> +++ b/tests/qemu-iotests/277
>> @@ -27,7 +27,8 @@ from iotests import file_path, log
>> iotests.script_initialize()
>>
>>
>> -nbd_sock, conf_file = file_path('nbd-sock', 'nbd-fault-injector.conf')
>> +conf_file = file_path('nbd-fault-injector.conf')
>> +nbd_sock = file_path('nbd-sock', base_dir=iotests.sock_dir)
>>
>>
>> def make_conf_file(event):
>> --
>> 2.39.3
>>
I would say that potentially the same code is present
in 264, it is :
disk_a, disk_b, nbd_sock = file_path('disk_a', 'disk_b', 'nbd-sock')
nbd_uri = 'nbd+unix:///?socket=' + nbd_sock
next prev parent reply other threads:[~2024-01-24 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 16:22 [PATCH] iotests/277: Use iotests.sock_dir for socket creation Andrey Drobyshev
2024-01-24 17:43 ` Eric Blake
2024-01-24 17:59 ` Denis V. Lunev [this message]
2024-01-25 13:54 ` Andrey Drobyshev
2024-01-26 11:28 ` Kevin Wolf
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=e513bffc-636e-4921-b87d-be67a52457f1@virtuozzo.com \
--to=den@virtuozzo.com \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).