linux-kernel - Re: [PATCH] usb: host: ohci-at91: suspend/resume ports after/before OHCI accesses

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: <20210624132304.GA528247@rowland.harvard.edu>
Date:   Thu, 24 Jun 2021 09:23:04 -0400
From:   Alan Stern <stern@...land.harvard.edu>
To:     Claudiu.Beznea@...rochip.com
Cc:     gregkh@...uxfoundation.org, Nicolas.Ferre@...rochip.com,
        alexandre.belloni@...tlin.com, Ludovic.Desroches@...rochip.com,
        Cristian.Birsan@...rochip.com, linux-usb@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: host: ohci-at91: suspend/resume ports after/before
 OHCI accesses

On Thu, Jun 24, 2021 at 06:40:25AM +0000, Claudiu.Beznea@...rochip.com wrote:
> On 23.06.2021 19:41, Alan Stern wrote:
> > Are there any systems beside the SAMA7G5 and others you tested which
> > might be affected by this patch?  Do they all work pretty much the
> > same way?  (I want to make sure no others will be adversely affected
> > by this change.)
> 
> I tested it on SAMA7G5, SAMA5D2 and SAM9X60. I tested the suspend/resume
> to/from mem. On SAMA5D2 and SAM9X60 there is no clock provided by
> transceiver A to OHCI. I encountered no issues on tested systems. These IPs
> are also present on SAMA5D3 and SAMA5D4 systems which I haven't tested as I
> expect to behave as SAMA5D2 (as the clocking scheme is the same with
> SAMA5D2). I can also try it on a SAMA5D3 (I don't have a SAMA5D4 with me at
> the moment), tough, just to be sure nothing is broken there too.

That doesn't answer my question.  I asked if there were any systems 
which might be affected by your patch, and you listed a bunch of 
systems that _aren't_ affected (that is, they continue to work 
properly).

What systems might run into trouble with this patch?

Alan Stern