From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, quintela@redhat.com,
stefanha@gmail.com, qemu-devel@nongnu.org,
lcapitulino@redhat.com, pbonzini@redhat.com, dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH V2 04/10] oslib-win32: add lock for time functions
Date: Tue, 08 Jan 2013 10:27:59 +0800 [thread overview]
Message-ID: <50EB842F.1060606@linux.vnet.ibm.com> (raw)
In-Reply-To: <50EB0219.8040605@weilnetz.de>
> Am 07.01.2013 08:28, schrieb Wenchao Xia:
>> This patch adding lock for calling gmtime() and localtime()
>> on windows. If no other lib linked into qemu would call those
>> two function itself, then they are thread safe now on windows.
>>
>> Signed-off-by: Wenchao Xia<xiawenc@linux.vnet.ibm.com>
>> ---
>> oslib-win32.c | 12 ++++++++++--
>> 1 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/oslib-win32.c b/oslib-win32.c
>> index e7e283e..344e3dd 100644
>> --- a/oslib-win32.c
>> +++ b/oslib-win32.c
>> @@ -74,27 +74,35 @@ void qemu_vfree(void *ptr)
>> VirtualFree(ptr, 0, MEM_RELEASE);
>> }
>>
>> -/* FIXME: add proper locking */
>> +/* WARN: if other lib call gmtime() itself, then it is not thread
>> safe. */
>> struct tm *gmtime_r(const time_t *timep, struct tm *result)
>> {
>> + static GStaticMutex lock = G_STATIC_MUTEX_INIT;
>> +
>> + g_static_mutex_lock(&lock);
>> struct tm *p = gmtime(timep);
>> memset(result, 0, sizeof(*result));
>> if (p) {
>> *result = *p;
>> p = result;
>> }
>> + g_static_mutex_unlock(&lock);
>> return p;
>> }
>>
>> -/* FIXME: add proper locking */
>> +/* WARN: if other lib call localtime() itself, then it is not thread
>> safe. */
>> struct tm *localtime_r(const time_t *timep, struct tm *result)
>> {
>> + static GStaticMutex lock = G_STATIC_MUTEX_INIT;
>> +
>> + g_static_mutex_lock(&lock);
>> struct tm *p = localtime(timep);
>> memset(result, 0, sizeof(*result));
>> if (p) {
>> *result = *p;
>> p = result;
>> }
>> + g_static_mutex_unlock(&lock);
>> return p;
>> }
>>
>
> Please remove this patch from the series:
>
> * It is unrelated to the other patches but tries to fix
> a separate problem. Even if the code now calls localtime_r,
> it is not worse than the old patch version which called
> localtime for MinGW.
>
OK.
> * localtime_r and gmtime_r use the same global storage,
> so they must use a common mutex instead of one mutex
> for each function.
>
Thanks for tipping that, I did not know this before.
> * Even with a common mutex, the comment
> "FIXME: add proper locking" still applies because there
> is no common locking mechanism for asctime, ctime, gmtime
> and localtime. I prefer FIXME or TODO comments for
> code deficiencies, not WARN.
>
> The correct fix can only be done in MinGW / MinGW-w64.
>
I think so, will keeps "FIXME" comments and change the code
calling gmtime()/localtime().
> Improving QEMU in a separate series with correct locking
> is ok if that series also removes the remaining
> calls of gmtime and localtime. Then the risk of
> reentrancy problems is reduced to a minimum.
>
> Regards
>
> Stefan W.
>
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2013-01-08 2:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 7:27 [Qemu-devel] [PATCH V2 00/10] snapshot: take block snapshots in unified way Wenchao Xia
2013-01-07 7:27 ` [Qemu-devel] [PATCH V2 01/10] block: export function bdrv_find_snapshot() Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 02/10] block: add function deappend() Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 03/10] error: add function error_set_check() Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 04/10] oslib-win32: add lock for time functions Wenchao Xia
2013-01-07 17:12 ` Stefan Weil
2013-01-08 2:27 ` Wenchao Xia [this message]
2013-01-07 7:28 ` Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 05/10] snapshot: design of internal common API to take snapshots Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 06/10] snapshot: implemention " Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 07/10] snapshot: qmp use new internal API for external snapshot transaction Wenchao Xia
2013-01-09 12:44 ` Stefan Hajnoczi
2013-01-10 3:21 ` Wenchao Xia
2013-01-10 12:41 ` Stefan Hajnoczi
2013-01-11 6:22 ` Wenchao Xia
2013-01-11 9:12 ` Stefan Hajnoczi
2013-01-14 2:56 ` Wenchao Xia
2013-01-14 10:06 ` Stefan Hajnoczi
2013-01-15 7:03 ` Wenchao Xia
2013-03-12 8:30 ` Wenchao Xia
2013-03-12 15:43 ` Stefan Hajnoczi
2013-03-13 1:36 ` Wenchao Xia
2013-03-13 8:42 ` Stefan Hajnoczi
2013-03-13 10:18 ` Kevin Wolf
2013-03-14 5:08 ` Wenchao Xia
2013-03-14 8:22 ` Kevin Wolf
2013-03-18 10:00 ` Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 08/10] snapshot: qmp add internal snapshot transaction interface Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 09/10] snapshot: qmp add blockdev-snapshot-internal-sync interface Wenchao Xia
2013-01-07 7:28 ` [Qemu-devel] [PATCH V2 10/10] snapshot: hmp add internal snapshot support for block device Wenchao Xia
2013-01-09 22:34 ` [Qemu-devel] [PATCH V2 00/10] snapshot: take block snapshots in unified way Eric Blake
2013-01-10 6:01 ` Wenchao Xia
2013-01-11 13:56 ` Luiz Capitulino
2013-01-14 2:09 ` Wenchao Xia
2013-01-14 10:08 ` Stefan Hajnoczi
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=50EB842F.1060606@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=dietmar@proxmox.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.com \
--cc=sw@weilnetz.de \
/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).