Messages in this thread | | | From | Suren Baghdasaryan <> | Date | Mon, 26 Feb 2024 09:13:17 -0800 | Subject | Re: [PATCH v4 13/36] lib: prevent module unloading if memory is not freed |
| |
On Mon, Feb 26, 2024 at 8:58 AM Vlastimil Babka <vbabka@suse.cz> wrote: > > 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?
Yes, that sounds reasonable. I'll add a pr_warn() in the next version. Thanks!
> > -- > To unsubscribe from this group and stop receiving emails from it, send an email to kernel-team+unsubscribe@android.com. >
| |