linux-kernel - Re: [PATCH v4 1/3] Revert "Revert "usb: gadget: udc: core: Invoke usb_gadget

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: <6547e73e-81e4-4a29-babf-13f852f1eb8b@rowland.harvard.edu>
Date:   Mon, 29 May 2023 20:42:18 -0400
From:   Alan Stern <stern@...land.harvard.edu>
To:     Badhri Jagan Sridharan <badhri@...gle.com>
Cc:     gregkh@...uxfoundation.org, colin.i.king@...il.com,
        xuetao09@...wei.com, quic_eserrao@...cinc.com,
        water.zhangjiantao@...wei.com, peter.chen@...escale.com,
        balbi@...com, francesco@...cini.it, alistair@...stair23.me,
        stephan@...hold.net, bagasdotme@...il.com, luca@...tu.xyz,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org
Subject: Re: [PATCH v4 1/3] Revert "Revert "usb: gadget: udc: core: Invoke
 usb_gadget_connect only when started""

On Mon, May 29, 2023 at 11:48:14PM +0000, Badhri Jagan Sridharan wrote:
> This reverts commit f22e9b67f19ccc73de1ae04375d4b30684e261f8.
> 
> The regression reported in
> https://lore.kernel.org/all/ZF4bMptC3Lf2Hnee@gerhold.net/ is being
> fixed in
> commit 7d7863db7cc0 ("usb: gadget: udc: core: Offload usb_udc_vbus_handler processing").

What commit is that?  It doesn't exist yet, at least, not in the 
mainline kernel.

> Hence reverting the revert.
> 
> Signed-off-by: Badhri Jagan Sridharan <badhri@...gle.com>

No!  Do not do this.  If you do, there will again be a version of the 
kernel that has the bug that caused the revert in the first place.  Even 
if it's only temporary, it could still affect people who are (for 
example) trying to run bisections.

Instead, reorder the patches.  First fix the underlying problem that 
led to the deadlocks.  Once that's in good shape then you can safely 
make this change.

Alan Stern