From: Sasha Levin <levinsasha928@gmail.com>
To: penberg@kernel.org
Cc: gorcunov@openvz.org, mingo@kernel.org, asias.hejun@gmail.com,
kvm@vger.kernel.org, Sasha Levin <levinsasha928@gmail.com>
Subject: [PATCH 1/4] kvm tools: fix sigsegv in irq__exit
Date: Wed, 9 May 2012 14:24:45 +0200 [thread overview]
Message-ID: <1336566288-5777-1-git-send-email-sasha.levin@oracle.com> (raw)
From: Sasha Levin <levinsasha928@gmail.com>
We free the structure, but never remove them from the tree or list, then
we freed them the next time we ran through that structure.
This patch also simplifies irq__exit a bit.
Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
---
tools/kvm/x86/irq.c | 17 +++++------------
1 files changed, 5 insertions(+), 12 deletions(-)
diff --git a/tools/kvm/x86/irq.c b/tools/kvm/x86/irq.c
index dc07f28..e83df99 100644
--- a/tools/kvm/x86/irq.c
+++ b/tools/kvm/x86/irq.c
@@ -179,25 +179,18 @@ int irq__exit(struct kvm *kvm)
free(irq_routing);
- ent = rb_first(&pci_tree);
- for (;;) {
+ while ((ent = rb_first(&pci_tree))) {
struct pci_dev *dev;
- struct rb_node *next;
struct irq_line *line;
- struct list_head *node, *tmp;
-
- if (!ent)
- break;
-
- next = rb_next(ent);
dev = rb_entry(ent, struct pci_dev, node);
- list_for_each_safe(node, tmp, &dev->lines) {
- line = list_entry(node, struct irq_line, node);
+ while (!list_empty(&dev->lines)) {
+ line = list_first_entry(&dev->lines, struct irq_line, node);
+ list_del(&line->node);
free(line);
}
+ rb_erase(&dev->node, &pci_tree);
free(dev);
- ent = next;
}
return 0;
--
1.7.8.5
next reply other threads:[~2012-05-09 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 12:24 Sasha Levin [this message]
2012-05-09 12:24 ` [PATCH 2/4] kvm tools: use bitwise 'and' in kvm-ipc Sasha Levin
2012-05-09 12:24 ` [PATCH 3/4] kvm tools: use accessor function for virtio-9p FIDs Sasha Levin
2012-05-09 12:24 ` [PATCH 4/4] kvm tools: increase amount of " Sasha Levin
2012-05-09 12:29 ` [PATCH 1/4] kvm tools: fix sigsegv in irq__exit Pekka Enberg
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=1336566288-5777-1-git-send-email-sasha.levin@oracle.com \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@openvz.org \
--cc=kvm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=penberg@kernel.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).