VT-d: avoid infinite recursion on domain_context_mapping_one() error path

Despite the comment there infinite recursion was still possible, by
flip-flopping between two domains. This is because prev_dom is derived
from the DID found in the context entry, which was already updated by
the time error recovery is invoked. Simply introduce yet another mode
flag to prevent rolling back an in-progress roll-back of a prior
mapping attempt.

Also drop the existing recursion prevention for having been dead anyway:
Earlier in the function we already bail when prev_dom == domain.

Fixes: 8f41e481b4 ("VT-d: re-assign devices directly")
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
master commit: 99d829dba1
master date: 2022-04-07 12:31:16 +0200
This commit is contained in:
Jan Beulich committed 2022-04-08 15:28:36 +02:00
1 parent 02d095b2d3
commit efea4bdbd1
2 files changed
+6 -4

No files matched your search

+4 -3
View File
@@ -1636,7 +1636,7 @@ int domain_context_mapping_one(
if ( !seg && !rc )
rc = me_wifi_quirk(domain, bus, devfn, domid, pgd_maddr, mode);
if ( rc )
if ( rc && !(mode & MAP_ERROR_RECOVERY) )
{
if ( !prev_dom ||
/*
@@ -1646,11 +1646,12 @@ int domain_context_mapping_one(
*/
(prev_dom == dom_io && !pdev) )
domain_context_unmap_one(domain, iommu, bus, devfn);
else if ( prev_dom != domain ) /* Avoid infinite recursion. */
else
domain_context_mapping_one(prev_dom, iommu, bus, devfn, pdev,
DEVICE_DOMID(prev_dom, pdev),
DEVICE_PGTABLE(prev_dom, pdev),
mode & MAP_WITH_RMRR);
(mode & MAP_WITH_RMRR)
| MAP_ERROR_RECOVERY);
}
if ( prev_dom )
+2 -1
View File
@@ -29,7 +29,8 @@
#define MAP_WITH_RMRR (1u << 0)
#define MAP_OWNER_DYING (1u << 1)
#define MAP_SINGLE_DEVICE (1u << 2)
#define UNMAP_ME_PHANTOM_FUNC (1u << 3)
#define MAP_ERROR_RECOVERY (1u << 3)
#define UNMAP_ME_PHANTOM_FUNC (1u << 4)
/* Allow for both IOAPIC and IOSAPIC. */
#define IO_xAPIC_route_entry IO_APIC_route_entry
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.