[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231115082138.2649870-1-liushixin2@huawei.com>
Date: Wed, 15 Nov 2023 16:21:36 +0800
From: Liu Shixin <liushixin2@...wei.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
Catalin Marinas <catalin.marinas@....com>,
Patrick Wang <patrick.wang.shcn@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kefeng Wang <wangkefeng.wang@...wei.com>
CC: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Liu Shixin <liushixin2@...wei.com>
Subject: [PATCH 0/2] Fix invalid wait context of set_track_prepare()
Geert reported an invalid wait context[1] which is resulted by moving
set_track_prepare() inside kmemleak_lock. This is not allowed because
in RT mode, the spinlocks can be preempted but raw_spinlocks can not,
so it is not allowd to acquire spinlocks while holding raw_spinlocks.
The second patch fix same problem in kmemleak_update_trace().
Link: https://lore.kernel.org/linux-mm/CAMuHMdWj0UzwNaxUvcocTfh481qRJpOWwXxsJCTJfu1oCqvgdA@mail.gmail.com/ [1]
Liu Shixin (2):
Revert "mm/kmemleak: move the initialisation of object to
__link_object"
mm/kmemleak: move set_track_prepare() outside raw_spinlocks
mm/kmemleak.c | 40 ++++++++++++++++++++++------------------
1 file changed, 22 insertions(+), 18 deletions(-)
--
2.25.1
Powered by blists - more mailing lists