From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54707) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bMby5-0007Vf-0l for qemu-devel@nongnu.org; Mon, 11 Jul 2016 10:13:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bMby4-0001OA-5J for qemu-devel@nongnu.org; Mon, 11 Jul 2016 10:13:52 -0400 Date: Mon, 11 Jul 2016 16:13:45 +0200 From: Kevin Wolf Message-ID: <20160711141345.GD5553@noname.redhat.com> References: <20160711135452.11304-1-mreitz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160711135452.11304-1-mreitz@redhat.com> Subject: Re: [Qemu-devel] [PATCH] vvfat: Fix qcow write target driver specification List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org Am 11.07.2016 um 15:54 hat Max Reitz geschrieben: > First, bdrv_open_child() expects all options for the child to be > prefixed by the child's name (and a separating dot). Second, > bdrv_open_child() does not take ownership of the QDict passed to it but > only extracts all options for the child, so if a QDict is created for > the sole purpose of passing it to bdrv_open_child(), it needs to be > freed afterwards. > > This patch makes vvfat adhere to both of these rules. > > Signed-off-by: Max Reitz Reviewed-by: Kevin Wolf