linux-kernel - Re: [PATCH] usb/core/hub.c: return immediately when hub_port

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 6 Mar 2014 22:47:18 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"xinhui.pan" <xinhuix.pan@...el.com>
Cc:	linux-kernel@...r.kernel.org, stern@...land.harvard.edu,
	sarah.a.sharp@...ux.intel.com, dan.j.williams@...el.com,
	burzalodowa@...il.com, yanmin_zhang@...ux.intel.com
Subject: Re: [PATCH] usb/core/hub.c: return immediately when hub_port_init
 hits timedout

On Fri, Mar 07, 2014 at 02:15:48PM +0800, xinhui.pan wrote:
> From: "xinhui.pan" <xinhuiX.pan@...el.com>

I doubt your name as a "." in it, right?

> some devices go crasy, we can't resume it even after reset.

I don't understand, what do you mean by this?  What exactly does a
device do, and why does it do it?  And what happens?

> This case will cause timeout again and again. What is worse, if there
> is a watchdog, panic will be generated as timer expires.

A watchdog where?

> To prevent this, we just return -ENODEV immediately. Later it will be
> re-enumerated.

What will cause it to be re-enumerated?

confused,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/