Re: [PATCH v4 13/36] lib: prevent module unloading if memory is not freed
From: Vlastimil Babka <hidden>
Date: 2024-02-26 16:58:42
Also in:
cgroups, linux-arch, linux-doc, linux-fsdevel, linux-iommu, linux-mm, lkml
On 2/21/24 20:40, Suren Baghdasaryan wrote:
Skip freeing module's data section if there are non-zero allocation tags because otherwise, once these allocations are freed, the access to their code tag would cause UAF. Signed-off-by: Suren Baghdasaryan <surenb@google.com>
I know that module unloading was never considered really supported etc. But should we printk something so the admin knows why it didn't unload, and can go check those outstanding allocations?