From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [Qemu-devel] [PATCH 06/11] qga: fail early for invalid time
Date: Tue, 7 Jul 2015 20:43:34 -0500 [thread overview]
Message-ID: <1436319819-17864-7-git-send-email-mdroth@linux.vnet.ibm.com> (raw)
In-Reply-To: <1436319819-17864-1-git-send-email-mdroth@linux.vnet.ibm.com>
From: Marc-André Lureau <marcandre.lureau@redhat.com>
It's possible to set system time with dates after 2070, however, it's
not possible to set the RTC. It has limitation to up to year
2070 (1970+100). In order to keep both clock in sync and before the
kernel complains on invalid values, bail out early.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
---
qga/commands-posix.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/qga/commands-posix.c b/qga/commands-posix.c
index c349d4b..675f4b4 100644
--- a/qga/commands-posix.c
+++ b/qga/commands-posix.c
@@ -154,6 +154,8 @@ void qmp_guest_set_time(bool has_time, int64_t time_ns, Error **errp)
/* If user has passed a time, validate and set it. */
if (has_time) {
+ GDate date = { 0, };
+
/* year-2038 will overflow in case time_t is 32bit */
if (time_ns / 1000000000 != (time_t)(time_ns / 1000000000)) {
error_setg(errp, "Time %" PRId64 " is too large", time_ns);
@@ -162,6 +164,11 @@ void qmp_guest_set_time(bool has_time, int64_t time_ns, Error **errp)
tv.tv_sec = time_ns / 1000000000;
tv.tv_usec = (time_ns % 1000000000) / 1000;
+ g_date_set_time_t(&date, tv.tv_sec);
+ if (date.year < 1970 || date.year >= 2070) {
+ error_setg_errno(errp, errno, "Invalid time");
+ return;
+ }
ret = settimeofday(&tv, NULL);
if (ret < 0) {
--
1.9.1
next prev parent reply other threads:[~2015-07-08 1:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 1:43 [Qemu-devel] [PULL v2 00/11] qemu-ga patches for 2.4.0 Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 01/11] qga/commands-posix: Fix bug in guest-fstrim Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 02/11] qga/qmp_guest_fstrim: Return per path fstrim result Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 03/11] Revert "guest agent: remove g_strcmp0 usage" Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 04/11] qga: add win32 library iphlpapi Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 05/11] qga: win32 qmp_guest_network_get_interfaces implementation Michael Roth
2015-07-08 1:43 ` Michael Roth [this message]
2015-07-08 1:43 ` [Qemu-devel] [PATCH 07/11] qga: added empty qmp_quest_get_fsinfo functionality Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 08/11] qga: added mountpoint and filesystem type for single volume Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 09/11] configure: add configure check for ntdddisk.h Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 10/11] qga: added bus type and disk location path Michael Roth
2015-07-08 1:43 ` [Qemu-devel] [PATCH 11/11] qga: added GuestPCIAddress information Michael Roth
-- strict thread matches above, loose matches on Subject: below --
2015-07-08 2:11 [Qemu-devel] [PULL v3 00/11] qemu-ga patches for 2.4.0 Michael Roth
2015-07-08 2:11 ` [Qemu-devel] [PATCH 06/11] qga: fail early for invalid time Michael Roth
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=1436319819-17864-7-git-send-email-mdroth@linux.vnet.ibm.com \
--to=mdroth@linux.vnet.ibm.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.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).