You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
commit be8250786ca94952a19ce87f98ad9906448bc9ef upstream.
When memory allocation profiling is disabled at runtime or due to an
error, shutdown_mem_profiling() is called: slab->obj_exts which
previously allocated remains.
It won't be cleared by unaccount_slab() because of
mem_alloc_profiling_enabled() not true. It's incorrect, slab->obj_exts
should always be cleaned up in unaccount_slab() to avoid following error:
[...]BUG: Bad page state in process...
..
[...]page dumped because: page still charged to cgroup
[[email protected]: fold need_slab_obj_ext() into its only user]
Fixes: 21c690a ("mm: introduce slabobj_ext to support slab object extensions")
Cc: [email protected]
Signed-off-by: Zhenhua Huang <[email protected]>
Acked-by: David Rientjes <[email protected]>
Acked-by: Harry Yoo <[email protected]>
Tested-by: Harry Yoo <[email protected]>
Acked-by: Suren Baghdasaryan <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Vlastimil Babka <[email protected]>
[surenb: fixed trivial merge conflict in alloc_tagging_slab_alloc_hook(),
skipped inlining free_slab_obj_exts() as it's already inline in 6.12]
Signed-off-by: Suren Baghdasaryan <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
(cherry picked from commit dab2a13059a475b6392550f882276e170fe2fcff)
Signed-off-by: Jack Vogel <[email protected]>
0 commit comments