From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uu1my-0002ot-Bj for qemu-devel@nongnu.org; Tue, 02 Jul 2013 10:42:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uu1mv-0008Tf-BG for qemu-devel@nongnu.org; Tue, 02 Jul 2013 10:42:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35715) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uu1mv-0008T8-4E for qemu-devel@nongnu.org; Tue, 02 Jul 2013 10:42:37 -0400 Message-ID: <51D2E767.9010106@redhat.com> Date: Tue, 02 Jul 2013 16:44:55 +0200 From: Laszlo Ersek MIME-Version: 1.0 References: <51D274DB.1080009@redhat.com> <20130702100903.43435654@redhat.com> In-Reply-To: <20130702100903.43435654@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4 08/10] qemu-ga: call Windows VSS requester in fsfreeze command handler List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: "libaiqing@huawei.com" , "stefanha@gmail.com" , "qemu-devel@nongnu.org" , "mdroth@linux.vnet.ibm.com" , "vrozenfe@redhat.com" , Tomoki Sekiyama , "pbonzini@redhat.com" , Seiji Aguchi , "areis@redhat.com" On 07/02/13 16:09, Luiz Capitulino wrote: > On Tue, 02 Jul 2013 08:36:11 +0200 > Laszlo Ersek wrote: > >> On 07/01/13 19:59, Tomoki Sekiyama wrote: >>> On 7/1/13 9:29 , "Laszlo Ersek" wrote: >>> >>>>> +error: >>>>> + qmp_guest_fsfreeze_thaw(NULL); >>>> >>>> Passing NULL here as "errp" concerns me slightly. I've been assuming >>>> that "errp" is never NULL due to the outermost QMP layer always wanting >>>> to receive errors and to serialize them. >>>> >>>> Specifically, a NULL "errp" would turn all error_set*(errp, ...) calls >>>> into no-ops under qmp_guest_fsfreeze_thaw(), and all error_is_set(errp) >>>> questions would answer with false. That said, nothing seems to be >>>> affected right now. >>>> >>>> Maybe a dummy local variable would be more future-proof... OTOH it would >>>> be stylistically questionable :) >>> >>> OK, then it should be: >>> Error *local_err = NULL; >>> ... >>> error: >>> qmp_guest_fsfreeze_thaw(&local_err); >>> if (error_is_set(&local_err)) { >>> error_free(local_err); >>> } >> >> I think so, yes. >> >> You could also log it before freeing it I guess: >> >> g_debug("cleanup thaw: %s", error_get_pretty(local_err)); >> >> or some such, but it's probably not important. > > I'd rather do something like that, otherwise it doesn't seem to > make sense to pass Error as qmp_guest_fsfreeze_thaw() does > use a local Error. No, the win32 version of qmp_guest_fsfreeze_thaw() being added by this patch doesn't. Thanks, Laszlo