linux-kernel - Re: [PATCH 0/3] usb: dwc2: Fixes and improvements

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:   Wed, 13 Jan 2021 19:07:15 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Doug Anderson <dianders@...omium.org>
Cc:     Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
        Paul Zimmerman <Paul.Zimmerman@...opsys.com>,
        Felipe Balbi <balbi@...com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Nick Hudson <skrll@...bsd.org>,
        Linux USB List <linux-usb@...r.kernel.org>,
        Minas Harutyunyan <hminas@...opsys.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] usb: dwc2: Fixes and improvements

On Wed, Jan 13, 2021 at 03:20:55PM -0800, Doug Anderson wrote:
> Hi,
> 
[ ... ]
> 
> It's been long enough ago that I've forgotten where this was left off,
> but IIRC the 3 patches that you have here are all fine to land (and
> have my Reviewed-by tag).  However, I think Guenter was still tracking
> down additional problems.  Guenter: does that match your recollection?
> 
> It looks like there are still bugs open for this on our public bug tracker:
> 
> https://issuetracker.google.com/issues/172208170
> https://issuetracker.google.com/issues/172216241
> 
> ...but, as Guenter said, I don't think there's anyone actively working on them.
> 
> I'm not really doing too much with dwc2 these days either and don't
> currently have good HW setup for testing, so for the most part I'll
> leave it to you.  I wanted to at least summarize what I remembered,
> though!  :-)
> 

The patches in this series still match what I had in my latest test code,
so it makes sense to move forward with them. I don't think I ever found
an acceptable version of the DMA alignment code.

Guenter