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: <2025041738-rocklike-undergrad-14d6@gregkh>
Date: Thu, 17 Apr 2025 16:37:50 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Cal Peake <cp@...olutedigital.net>
Cc: Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Vishal Annapurve <vannapurve@...gle.com>,
	"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
	Alex Williamson <alex.williamson@...hat.com>
Subject: Re: [STABLE] 6.12.23: vfio error (was: arch/x86/coco/tdx/tdx.c build
 error)

On Mon, Apr 14, 2025 at 07:55:06PM -0400, Cal Peake wrote:
> On Sun, 13 Apr 2025, Cal Peake wrote:
> 
> > After booting the new kernel, I get errors trying to do vfio passthrough:
> > 
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.3, no available reset mechanism.
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.2, no available reset mechanism.
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.1, no available reset mechanism.
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.0, no available reset mechanism.
> 
> This was resolved by Alex Williamson, with his patch:
> 
> https://lore.kernel.org/lkml/20250414211828.3530741-1-alex.williamson@redhat.com/

Is this in Linus's tree yet?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ