linux-kernel - Re: [PATCH v1 1/1] PCI: Enable INTx quirk for ATI PCIe-USB adapter

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:   Tue, 15 Mar 2022 12:09:08 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org, micklorain@...tonmail.com
Subject: Re: [PATCH v1 1/1] PCI: Enable INTx quirk for ATI PCIe-USB adapter

On Mon, Mar 14, 2022 at 02:42:53PM -0500, Bjorn Helgaas wrote:
> On Mon, Mar 14, 2022 at 12:14:48PM +0200, Andy Shevchenko wrote:
> > ATI PCIe-USB adapter advertises MSI, but it doesn't work if INTx is disabled.
> > Enable the respective quirk as it's done for other ATI devices on this chipset,
> > 
> > Fixes: 306c54d0edb6 ("usb: hcd: Try MSI interrupts on PCI devices")
> 
> This is interesting because there must be a TON of these AMD/ATI SB600
> USB devices in the field, and 306c54d0edb6 was merged in July 2020 and
> appeared in v5.9.
> 
> So why would we only get a report now, in February 2022?  Is there
> some change more recent than 306c54d0edb6 that exposed this problem?

I think it's a rhetorical question. To me it's as simple as the latency
between getting the change into the kernel.

However, I'm a bit worried that in case of ATI there are not so many
platforms that are kept up-to-dated.

-- 
With Best Regards,
Andy Shevchenko