From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Hans de Goede <hdegoede@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 05/14] ehci: Don't access packet after freeing it
Date: Fri, 16 Nov 2012 14:44:38 +0100 [thread overview]
Message-ID: <1353073487-19233-6-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1353073487-19233-1-git-send-email-kraxel@redhat.com>
From: Hans de Goede <hdegoede@redhat.com>
ehci_state_writeback() will free the packet, so we should not access
the packet after calling ehci_state_writeback().
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/usb/hcd-ehci.c | 9 +++++----
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/hw/usb/hcd-ehci.c b/hw/usb/hcd-ehci.c
index ee6c9ae..a8b1a40 100644
--- a/hw/usb/hcd-ehci.c
+++ b/hw/usb/hcd-ehci.c
@@ -453,12 +453,13 @@ static EHCIPacket *ehci_alloc_packet(EHCIQueue *q)
static void ehci_free_packet(EHCIPacket *p)
{
if (p->async == EHCI_ASYNC_FINISHED) {
- int state = ehci_get_state(p->queue->ehci, p->queue->async);
+ EHCIQueue *q = p->queue;
+ int state = ehci_get_state(q->ehci, q->async);
/* This is a normal, but rare condition (cancel racing completion) */
fprintf(stderr, "EHCI: Warning packet completed but not processed\n");
- ehci_state_executing(p->queue);
- ehci_state_writeback(p->queue);
- ehci_set_state(p->queue->ehci, p->queue->async, state);
+ ehci_state_executing(q);
+ ehci_state_writeback(q);
+ ehci_set_state(q->ehci, q->async, state);
/* state_writeback recurses into us with async == EHCI_ASYNC_NONE!! */
return;
}
--
1.7.1
next prev parent reply other threads:[~2012-11-16 13:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 13:44 [Qemu-devel] [PULL for-1.3 00/14] usb patch queue Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 01/14] fix live migration Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 02/14] usb: Fix (another) bug in usb_packet_map() for IOMMU handling Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 03/14] usb-host: scan for usb devices when the vm starts Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 04/14] usb: host-linux: Ignore parsing errors of the device descriptors Gerd Hoffmann
2012-11-16 13:44 ` Gerd Hoffmann [this message]
2012-11-16 13:44 ` [Qemu-devel] [PATCH 06/14] ehci: Fixup q->qtdaddr after cancelling an already completed packet Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 07/14] ehci: Better detection for qtd-s linked in circles Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 08/14] ehci: Don't verify the next pointer for periodic qh-s and qtd-s Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 09/14] ehci: keep the frame timer running in case the guest asked for frame list rollover interrupts Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 10/14] ehci: handle dma errors Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 11/14] usb-redir: Only add actually in flight packets to the in flight queue Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 12/14] usb-redir: Set default debug level to warning Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 13/14] usb-host: update tracing Gerd Hoffmann
2012-11-16 13:44 ` [Qemu-devel] [PATCH 14/14] usb-host: fix splitted transfers Gerd Hoffmann
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=1353073487-19233-6-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=hdegoede@redhat.com \
--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).