From: Laszlo Ersek <lersek@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH RFC] qga: fence guest-set-time if hwclock not available
Date: Thu, 28 Nov 2019 15:06:03 +0100 [thread overview]
Message-ID: <68b5cca7-714f-ad8c-464e-699020bbae8c@redhat.com> (raw)
In-Reply-To: <20191128124532.GF248361@redhat.com>
On 11/28/19 13:45, Daniel P. Berrangé wrote:
> On Thu, Nov 28, 2019 at 01:36:58PM +0100, Cornelia Huck wrote:
>> The Posix implementation of guest-set-time invokes hwclock to
>> set/retrieve the time to/from the hardware clock. If hwclock
>> is not available, the user is currently informed that "hwclock
>> failed to set hardware clock to system time", which is quite
>> misleading. This may happen e.g. on s390x, which has a different
>> timekeeping concept anyway.
>>
>> Let's check for the availability of the hwclock command and
>> return QERR_UNSUPPORTED for guest-set-time if it is not available.
>>
>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
>> ---
>>
>> Not sure if that is the correct approach, but the current error
>> message is really quite confusing.
>
> I guess the alternative is to just #ifndef __s390x__ the whole
> impl of the qmp_guest_set_time method, but I don't have a
> strong opinion on which is best.
>
>>
>> Gave it a quick test with an s390x and an x86_64 guest; invoking
>> 'virsh domtime <value>' now fails with 'not currently supported'
>> on s390x and continues to work as before on x86_64.
>>
>> ---
>> qga/commands-posix.c | 20 +++++++++++++++++++-
>> 1 file changed, 19 insertions(+), 1 deletion(-)
>>
>> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
>> index 1c1a165daed8..bd298a38b716 100644
>> --- a/qga/commands-posix.c
>> +++ b/qga/commands-posix.c
>> @@ -149,6 +149,13 @@ int64_t qmp_guest_get_time(Error **errp)
>> return tq.tv_sec * 1000000000LL + tq.tv_usec * 1000;
>> }
>>
>> +static int check_hwclock_available(const char *path)
>> +{
>> + struct stat st;
>> +
>> + return (stat(path, &st) < 0) ? 0 : 1;
>> +}
>> +
>> void qmp_guest_set_time(bool has_time, int64_t time_ns, Error **errp)
>> {
>> int ret;
>> @@ -156,6 +163,17 @@ void qmp_guest_set_time(bool has_time, int64_t time_ns, Error **errp)
>> pid_t pid;
>> Error *local_err = NULL;
>> struct timeval tv;
>> + const char *hwclock_path = "/sbin/hwclock";
slight style / semantics improvement could be
static const char hwclock_path[] = "/sbin/hwclock";
Thanks
Laszlo
>> + static int hwclock_available = -1;
>> +
>> + if (hwclock_available < 0) {
>> + hwclock_available = check_hwclock_available(hwclock_path);
>
> Could do this inline with:
>
> hwclock_available = (access(hwclock_available, X_OK) == 0);
>
> getting a slightly better result as this check for it being
> executable as well as existing.
>
>> + }
>> +
>> + if (!hwclock_available) {
>> + error_setg(errp, QERR_UNSUPPORTED);
>> + return;
>> + }
>>
>> /* If user has passed a time, validate and set it. */
>> if (has_time) {
>> @@ -195,7 +213,7 @@ void qmp_guest_set_time(bool has_time, int64_t time_ns, Error **errp)
>>
>> /* Use '/sbin/hwclock -w' to set RTC from the system time,
>> * or '/sbin/hwclock -s' to set the system time from RTC. */
>> - execle("/sbin/hwclock", "hwclock", has_time ? "-w" : "-s",
>> + execle(hwclock_path, "hwclock", has_time ? "-w" : "-s",
>> NULL, environ);
>> _exit(EXIT_FAILURE);
>> } else if (pid < 0) {
>> --
>> 2.21.0
>>
>>
>
> Regards,
> Daniel
>
prev parent reply other threads:[~2019-11-28 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 12:36 [PATCH RFC] qga: fence guest-set-time if hwclock not available Cornelia Huck
2019-11-28 12:45 ` Daniel P. Berrangé
2019-11-28 12:49 ` Cornelia Huck
2019-11-28 14:41 ` Daniel P. Berrangé
2019-11-28 14:06 ` Laszlo Ersek [this message]
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=68b5cca7-714f-ad8c-464e-699020bbae8c@redhat.com \
--to=lersek@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--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).