Messages in this thread | | | Date | Mon, 26 Feb 2024 17:58:40 +0100 | Subject | Re: [PATCH v4 13/36] lib: prevent module unloading if memory is not freed | From | Vlastimil Babka <> |
| |
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?
| |