linux-kernel - Re: [RFC PATCH] xhci: do not halt the secondary HCD

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]

Message-ID: <20160919070346.GA29827@kroah.com>
Date:   Mon, 19 Sep 2016 09:03:46 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Joel Stanley <joel@....id.au>,
        Mathias Nyman <mathias.nyman@...el.com>
Cc:     linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] xhci: do not halt the secondary HCD

On Mon, Sep 19, 2016 at 04:05:45PM +0930, Joel Stanley wrote:
> We can't halt the secondary HCD, because it's also the primary HCD,
> which will cause problems if we have devices attached to the primary
> HCD, like a keyboard.
> 
> We've been carrying this in our Linux-as-a-bootloader environment for a little
> while now. The machines all have the same TI TUSB73x0 part, and when we kexec
> the devices don't come back until a system power cycle.
> 
> I'd like some advice on an acceptable way to upstream the fix, so that the xhci
> device survives kexec.

Any reason you didn't cc: Mathias?

And have you tried 4.8-rc kernels?  I thought we just fixed an issue
around secondary HCDs...

thanks,

greg k-h