From: Olaf Hering <olaf@aepfle.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Cc: Sasha Levin <sashal@kernel.org>,
linux-hyperv@vger.kernel.org (open list:Hyper-V CORE AND DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH v2] tools/hv: async name resolution in kvp_daemon
Date: Wed, 13 Nov 2019 17:00:21 +0100 [thread overview]
Message-ID: <20191113170021.2e98f1fb.olaf@aepfle.de> (raw)
In-Reply-To: <20191113155400.25456-1-olaf@aepfle.de>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Am Wed, 13 Nov 2019 16:54:00 +0100
schrieb Olaf Hering <olaf@aepfle.de>:
> During this time all "FullyQualifiedDomainName" requests will be
> answered with an empty string.
> + strcpy(key_value, full_domain_name ? : "");
> strcpy(key_name, "FullyQualifiedDomainName");
KY, Haiyang, Stephen,
please check if the host side can actually handle such temporary, empty string.
If the tools cache the first result, the implemented approach can not work.
If that is indeed the case, is there some sort of -ERETRY in the protocol?
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-13 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 15:54 [PATCH v2] tools/hv: async name resolution in kvp_daemon Olaf Hering
2019-11-13 16:00 ` Olaf Hering [this message]
2020-01-03 13:31 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2021-03-19 14:41 Olaf Hering
2021-03-19 14:46 ` Olaf Hering
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=20191113170021.2e98f1fb.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
/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).