linux-kernel - Re: [PATCH v2] PCI: Mark LSI FW643 to avoid bus reset

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: <20240327150119.GA1502858@bhelgaas>
Date: Wed, 27 Mar 2024 10:01:19 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, edmund.raile@...ton.me
Subject: Re: [PATCH v2] PCI: Mark LSI FW643 to avoid bus reset

On Tue, Mar 26, 2024 at 10:18:58PM +0900, Takashi Sakamoto wrote:
> On Mon, Mar 25, 2024 at 09:41:49AM -0500, Bjorn Helgaas wrote:
> > So even without this patch, you are able to pass the FW643 to a VM
> > with VFIO, and you don't see any issues caused by VFIO resetting the
> > device?
>  
> Absolutely yes, at least in my VM, for recent years to maintain Linux
> FireWire subsystem and ALSA firewire stack.

So there must be something different between your system and Edmund's.
Maybe we can refine the quirk so it avoids the SBR on Edmund's system
but not yours.

Can you both collect the output of "sudo lspci -vvv" so we can try to
figure out the difference?  Also a complete dmesg log would be helpful
and would contain DMI information that we might need if this is
firmware dependent.

> > Can you collect the output of:
> > 
> >   $ find /sys/devices -name reset_method | xargs grep .

Edmund, could you run this command, too?

Thanks,
  Bjorn