From: Greg KH <gregkh@linuxfoundation.org>
To: Yu Chen <chenyu56@huawei.com>
Cc: mathias.nyman@intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, fanning4@hisilicon.com,
lirui39@hisilicon.com, yangdi10@hisilicon.com,
wangbinghui@hisilicon.com, groeck@google.com,
john.stultz@linaro.org
Subject: Re: [PATCH] usb:xhci fix panic in xhci_free_virt_devices_depth_first
Date: Mon, 6 Nov 2017 08:59:44 +0100 [thread overview]
Message-ID: <20171106075944.GA19812@kroah.com> (raw)
In-Reply-To: <20171106032855.16736-1-chenyu56@huawei.com>
On Mon, Nov 06, 2017 at 11:28:55AM +0800, Yu Chen wrote:
> From: Yu Chen <chenyu56@huawei.com>
>
> Check vdev->real_port 0 to avoid panic
> [ 9.261347] [<ffffff800884a390>] xhci_free_virt_devices_depth_first+0x58/0x108
> [ 9.261352] [<ffffff800884a814>] xhci_mem_cleanup+0x1bc/0x570
> [ 9.261355] [<ffffff8008842de8>] xhci_stop+0x140/0x1c8
> [ 9.261365] [<ffffff80087ed304>] usb_remove_hcd+0xfc/0x1d0
> [ 9.261369] [<ffffff80088551c4>] xhci_plat_remove+0x6c/0xa8
> [ 9.261377] [<ffffff80086e928c>] platform_drv_remove+0x2c/0x70
> [ 9.261384] [<ffffff80086e6ea0>] __device_release_driver+0x80/0x108
> [ 9.261387] [<ffffff80086e7a1c>] device_release_driver+0x2c/0x40
> [ 9.261392] [<ffffff80086e5f28>] bus_remove_device+0xe0/0x120
> [ 9.261396] [<ffffff80086e2e34>] device_del+0x114/0x210
> [ 9.261399] [<ffffff80086e9e00>] platform_device_del+0x30/0xa0
> [ 9.261403] [<ffffff8008810bdc>] dwc3_otg_work+0x204/0x488
> [ 9.261407] [<ffffff80088133fc>] event_work+0x304/0x5b8
> [ 9.261414] [<ffffff80080e31b0>] process_one_work+0x148/0x490
> [ 9.261417] [<ffffff80080e3548>] worker_thread+0x50/0x4a0
> [ 9.261421] [<ffffff80080e9ea0>] kthread+0xe8/0x100
> [ 9.261427] [<ffffff8008083680>] ret_from_fork+0x10/0x50
>
> The problem can occur if xhci_plat_remove() is called shortly after
> xhci_plat_probe(). While xhci_free_virt_devices_depth_first been
> called before the device has been setup and get real_port initialized.
> The problem occurred on Hikey960 and was reproduced by Guenter Roeck
> on Kevin with chromeos-4.4.
>
> Cc: Guenter Roeck <groeck@google.com>
> Signed-off-by: Fan Ning <fanning4@hisilicon.com>
> Signed-off-by: Li Rui <lirui39@hisilicon.com>
> Signed-off-by: yangdi <yangdi10@hisilicon.com>
> Signed-off-by: Yu Chen <chenyu56@huawei.com>
>
>
> ---
> drivers/usb/host/xhci-mem.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/usb/host/xhci-mem.c b/drivers/usb/host/xhci-mem.c
> index 2a82c927ded2..295789d993b0 100644
> --- a/drivers/usb/host/xhci-mem.c
> +++ b/drivers/usb/host/xhci-mem.c
> @@ -947,6 +947,11 @@ void xhci_free_virt_devices_depth_first(struct xhci_hcd *xhci, int slot_id)
> if (!vdev)
> return;
>
> + if (WARN_ON(!vdev->real_port)) {
> + xhci_warn(xhci, "Bad vdev->real_port\n");
Why warn twice? What will that help?
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-06 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 3:28 [PATCH] usb:xhci fix panic in xhci_free_virt_devices_depth_first Yu Chen
2017-11-06 7:59 ` Greg KH [this message]
2017-11-06 8:07 ` Chen Yu
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=20171106075944.GA19812@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chenyu56@huawei.com \
--cc=fanning4@hisilicon.com \
--cc=groeck@google.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lirui39@hisilicon.com \
--cc=mathias.nyman@intel.com \
--cc=wangbinghui@hisilicon.com \
--cc=yangdi10@hisilicon.com \
/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.