+34
−5
+1
−0
+1
−0
+12
−2
+2
−1
Loading
stable inclusion from stable-v6.6.33 commit 0636b34b44589b142700ac137b5f69802cfe2e37 category: bugfix bugzilla: https://gitee.com/src-openeuler/kernel/issues/IA6SA1 CVE: CVE-2024-38570 Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0636b34b44589b142700ac137b5f69802cfe2e37 -------------------------------- [ Upstream commit d98779e687726d8f8860f1c54b5687eec5f63a73 ] When a DLM lockspace is released and there ares still locks in that lockspace, DLM will unlock those locks automatically. Commit fb6791d1 started exploiting this behavior to speed up filesystem unmount: gfs2 would simply free glocks it didn't want to unlock and then release the lockspace. This didn't take the bast callbacks for asynchronous lock contention notifications into account, which remain active until until a lock is unlocked or its lockspace is released. To prevent those callbacks from accessing deallocated objects, put the glocks that should not be unlocked on the sd_dead_glocks list, release the lockspace, and only then free those glocks. As an additional measure, ignore unexpected ast and bast callbacks if the receiving glock is dead. Fixes: fb6791d1 ("GFS2: skip dlm_unlock calls in unmount") Signed-off-by:Andreas Gruenbacher <agruenba@redhat.com> Cc: David Teigland <teigland@redhat.com> Signed-off-by:
Sasha Levin <sashal@kernel.org> Conflicts: fs/gfs2/glock.c fs/gfs2/glock.h fs/gfs2/incore.h fs/gfs2/lock_dlm.c fs/gfs2/ops_fstype.c [Resolve conflicts due to several refactor patches not merged.] Signed-off-by:
Zeng Heng <zengheng4@huawei.com>