Re: [PATCH v2 20/22] iommu/tegra241-cmdqv: Do not statically map LVCMDQs

On 26-04-2025 11:28, Nicolin Chen wrote:

However, with the user-owned VINTF support, it exposes a security concern: if user space VM only wants one LVCMDQ for a VINTF, statically mapping two LVCMDQs creates a hidden VCMDQ that user space could DoS attack by writing ramdon stuff to overwhelm the kernel with unhandleable IRQs.

typo ramdon -> random

Thus, to support the user-owned VINTF feature, a LVCMDQ mapping has to be done dynamically.

Thanks, Alok