linux-kernel - Re: [PATCH] PCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends

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] [day] [month] [year] [list]

Message-ID: <20250330145719.32280-1-spasswolf@web.de>
Date: Sun, 30 Mar 2025 16:57:17 +0200
From: Bert Karwatzki <spasswolf@....de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Bert Karwatzki <spasswolf@....de>,
	Roger Pau Monné <roger.pau@...rix.com>,
	"Daniel Gomez" <da.gomez@...nel.org>,
	Jürgen Groß <jgross@...e.com>,
	"Bjorn Helgaas" <helgaas@...nel.org>,
	linux-kernel@...r.kernel.org,
	xen-devel@...ts.xenproject.org,
	linux-pci@...r.kernel.org,
	"Ingo Molnar" <mingo@...hat.com>,
	"Borislav Petkov" <bp@...en8.de>,
	"Dave Hansen" <dave.hansen@...ux.intel.com>,
	x86@...nel.org,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] PCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends

This also fixes a timeout error in the nvme driver introduced by commit
c3164d2e0d1. In linux-next-2025032{5,6} booting hangs in about 50% of boot
attempts with the message:
nvme nvme1: I/O tag 4 (1004) QID 0 timeout, completion polled
nvme nvme0: I/O tag 20 (1014) QID 0 timeout, completion polled
after some more time I get a message about task udev-worker blocking for more
than 61 seconds and get dropped to an initramfs shell. I bisected this to
commit c3164d2e0d1. As this error does not occur in linux-next-20250328, I
searched for commits that might fix this error and indeed cherrypicking commit
dbc5d00074fd on top of linux-next-20250326 fixes the issue for me. No xen or
kvm was used in my case.

Bert Karwatzki