From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Matt Evans <matt@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 4/5] xhci: Add an assertion to check for virt_dev=0 bug.
Date: Mon, 28 Mar 2011 15:23:36 -0700 [thread overview]
Message-ID: <20110328222336.GE8065@xanatos> (raw)
In-Reply-To: <4D8C47D2.9010501@ozlabs.org>
On Fri, Mar 25, 2011 at 06:44:18PM +1100, Matt Evans wrote:
> During a "plug-unplug" stress test on an NEC xHCI card, a null pointer
> dereference was observed. xhci_address_device() dereferenced a null
> virt_dev (possibly an erroneous udev->slot_id?); this patch adds a WARN_ON &
> message to aid debug if it can be recreated.
Hmm, that's interesting. I haven't seen any null pointer dereferences
during my tests, but perhaps I'm not being ADDH enough about randomly
unplugging devices. :) Let me know if you trigger this again.
Sarah Sharp
> Signed-off-by: Matt Evans <matt@ozlabs.org>
> ---
> drivers/usb/host/xhci.c | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index 88e6298..7d43456 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -2542,6 +2542,17 @@ int xhci_address_device(struct usb_hcd *hcd, struct usb_device *udev)
>
> virt_dev = xhci->devs[udev->slot_id];
>
> + if (WARN_ON(!virt_dev)) {
> + /*
> + * In plug/unplug torture test with an NEC controller,
> + * a zero-dereference was observed once due to virt_dev = 0.
> + * Print useful debug rather than crash if it is observed again!
> + */
> + xhci_warn(xhci, "Virt dev invalid for slot_id 0x%x!\n",
> + udev->slot_id);
> + return -EINVAL;
> + }
> +
> slot_ctx = xhci_get_slot_ctx(xhci, virt_dev->in_ctx);
> /*
> * If this is the first Set Address since device plug-in or
> --
> 1.7.0.4
>
prev parent reply other threads:[~2011-03-28 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 7:44 [PATCH 4/5] xhci: Add an assertion to check for virt_dev=0 bug Matt Evans
2011-03-28 22:23 ` Sarah Sharp [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=20110328222336.GE8065@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@ozlabs.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.