From: Alex Chiang <achiang@hp.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>,
jbarnes@virtuousgeek.org, xyzzy@speakeasy.org, djwong@us.ibm.com,
shimada-yxb@necst.nec.co.jp, rjw@sisk.pl,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/11] PCI core learns hotplug
Date: Mon, 9 Mar 2009 14:37:19 -0600 [thread overview]
Message-ID: <20090309203719.GR32589@ldl.fc.hp.com> (raw)
In-Reply-To: <19f34abd0903091328q4471bb3he0c6e07fa32a6a1f@mail.gmail.com>
* Vegard Nossum <vegard.nossum@gmail.com>:
> 2009/3/9 Alex Chiang <achiang@hp.com>:
> >> It reproduces reliably if I do this:
> >>
> >> $ while true; do echo 1 > /sys/bus/pci/devices/0000\:00\:00.0/remove; done
> >
> > I was going to ask for lspci -v output so that I could see what
> > device 0000:00:00.0 might be, but I was able to reproduce
> > something similar on my machine.
> >
> > Can I ask why you're doing the above with a while loop? Just to
> > torture the code? Or something else?
>
> Yes, purely for the purpose of torture ;-)
Ok, just checking. :)
> I also found one more use-after-free error using kmemcheck:
>
> Hope this helps :-)
Yes, thanks a lot!
I'll work on these. Thanks for the excellent bug reports.
/ac
prev parent reply other threads:[~2009-03-09 20:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 5:48 [PATCH v3 00/11] PCI core learns hotplug Alex Chiang
2009-03-09 5:48 ` [PATCH v3 01/11] PCI: pci_is_root_bus helper Alex Chiang
2009-03-09 5:48 ` [PATCH v3 02/11] PCI: don't scan existing devices Alex Chiang
2009-03-09 5:48 ` [PATCH v3 03/11] PCI: pci_scan_slot() returns newly found devices Alex Chiang
2009-03-09 5:48 ` [PATCH v3 04/11] PCI: always scan child buses Alex Chiang
2009-03-09 5:49 ` [PATCH v3 05/11] PCI: beef up pci_do_scan_bus() Alex Chiang
2009-03-12 9:16 ` Kenji Kaneshige
2009-03-12 23:22 ` Alex Chiang
2009-03-13 9:11 ` Kenji Kaneshige
2009-03-15 16:48 ` Alex Chiang
2009-03-18 8:29 ` Kenji Kaneshige
2009-03-18 20:39 ` Alex Chiang
2009-03-19 2:15 ` Kenji Kaneshige
2009-03-09 5:49 ` [PATCH v3 06/11] PCI: Introduce /sys/bus/pci/rescan Alex Chiang
2009-03-09 5:49 ` [PATCH v3 07/11] PCI: Introduce /sys/bus/pci/devices/.../remove Alex Chiang
2009-03-09 18:52 ` Alex Chiang
2009-03-10 22:37 ` Alex Chiang
2009-03-11 4:08 ` Alex Chiang
2009-03-09 5:49 ` [PATCH v3 08/11] PCI: Introduce /sys/bus/pci/devices/.../rescan Alex Chiang
2009-03-09 5:49 ` [PATCH v3 09/11] PCI Hotplug: restore fakephp interface with complete reimplementation Alex Chiang
2009-03-09 5:49 ` [PATCH v3 10/11] PCI Hotplug: rename legacy_fakephp to fakephp Alex Chiang
2009-03-09 5:49 ` [PATCH v3 11/11] PCI Hotplug: schedule fakephp for feature removal Alex Chiang
2009-03-09 18:51 ` [PATCH v3 00/11] PCI core learns hotplug Alex Chiang
2009-03-09 19:30 ` Vegard Nossum
2009-03-09 19:52 ` Alex Chiang
2009-03-09 20:28 ` Vegard Nossum
2009-03-09 20:37 ` Alex Chiang [this message]
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=20090309203719.GR32589@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=djwong@us.ibm.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--cc=shimada-yxb@necst.nec.co.jp \
--cc=vegard.nossum@gmail.com \
--cc=xyzzy@speakeasy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.