From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsCKS-0000y6-ED for qemu-devel@nongnu.org; Thu, 27 Jun 2013 09:33:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsCKR-0003cy-7q for qemu-devel@nongnu.org; Thu, 27 Jun 2013 09:33:40 -0400 Message-ID: <51CC3F2F.4090608@redhat.com> Date: Thu, 27 Jun 2013 15:33:35 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <1372339512-28149-1-git-send-email-armbru@redhat.com> In-Reply-To: <1372339512-28149-1-git-send-email-armbru@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/1] qemu-char: Fix ID reuse after chardev-remove for qapi-based init List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org On 06/27/13 15:25, Markus Armbruster wrote: > Commit 2c5f488 introduced qapi-based character device initialization > as a new code path in qemu_chr_new_from_opts(). Unfortunately, it > failed to store parameter opts in the new chardev. Therefore, > qemu_chr_delete() doesn't delete it. Even though the device is gone, > its options linger, and any attempt to create another one with the > same ID fails. Reviewed-by: Gerd Hoffmann cheers, Gerd