diff options
| author | Jason Gunthorpe <[email protected]> | 2024-12-05 20:13:41 -0400 |
|---|---|---|
| committer | Joerg Roedel <[email protected]> | 2024-12-10 10:12:05 +0100 |
| commit | 4a552f7890f0870f6d9fd4fbc6c05cea7bfd4503 (patch) | |
| tree | 3ed54b9d4af1e61f82ed5e421cd8c6ad1b87e9a7 /tools/testing/selftests/bpf/prog_tests/prog_array_init.c | |
| parent | fac04efc5c793dccbd07e2d59af9f90b7fc0dca4 (diff) | |
iommu/amd: Put list_add/del(dev_data) back under the domain->lock
The list domain->dev_list is protected by the domain->lock spinlock.
Any iteration, addition or removal must be under the lock.
Move the list_del() up into the critical section. pdom_is_sva_capable(),
and destroy_gcr3_table() do not interact with the list element.
Wrap the list_add() in a lock, it would make more sense if this was under
the same critical section as adjusting the refcounts earlier, but that
requires more complications.
Fixes: d6b47dec3684 ("iommu/amd: Reduce domain lock scope in attach device path")
Signed-off-by: Jason Gunthorpe <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Joerg Roedel <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/prog_array_init.c')
0 files changed, 0 insertions, 0 deletions