Thread (96 messages) 96 messages, 9 authors, 2024-03-12

Re: [PATCH v4 13/36] lib: prevent module unloading if memory is not freed

From: Kent Overstreet <kent.overstreet@linux.dev>
Date: 2024-03-12 20:08:12
Also in: cgroups, linux-arch, linux-doc, linux-fsdevel, linux-iommu, linux-mm, lkml

On Tue, Mar 12, 2024 at 11:23:45AM -0700, Luis Chamberlain wrote:
On Mon, Feb 26, 2024 at 05:58:40PM +0100, Vlastimil Babka wrote:
quoted
On 2/21/24 20:40, Suren Baghdasaryan wrote:
quoted
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.
If its not supported then we should not have it on modules. Module
loading and unloading should just work, otherwise then this should not
work with modules and leave them in a zombie state.
Not have memory allocation profiling on modules?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help