[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1606895585-17382-1-git-send-email-Kuan-Ying.Lee@mediatek.com>
Date: Wed, 2 Dec 2020 15:53:04 +0800
From: Kuan-Ying Lee <Kuan-Ying.Lee@...iatek.com>
To: Andrey Ryabinin <aryabinin@...tuozzo.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Nicholas Tang <nicholas.tang@...iatek.com>,
Miles Chen <miles.chen@...iatek.com>
CC: <kasan-dev@...glegroups.com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>, <wsd_upstream@...iatek.com>,
Kuan-Ying Lee <Kuan-Ying.Lee@...iatek.com>
Subject: [PATCH v3 0/1] Fix object remain in offline per-cpu quarantine
This patch fixes object remain in the offline per-cpu quarantine as
describe below.
Free objects will get into per-cpu quarantine if enable generic KASAN.
If a cpu is offline and users use kmem_cache_destroy, kernel will detect
objects still remain in the offline per-cpu quarantine and report error.
Register a cpu hotplug function to remove all objects in the offline
per-cpu quarantine when cpu is going offline. Set a per-cpu variable
to indicate this cpu is offline.
Changes since v3:
- Add a barrier to ensure the ordering
- Rename the init function
Changes since v2:
- Thanks for Dmitry suggestion
- Remove unnecessary code
- Put offline variable into cpu_quarantine
- Use single qlist_free_all call instead of iteration over all slabs
- Add bug reporter in commit message
Kuan-Ying Lee (1):
kasan: fix object remain in offline per-cpu quarantine
mm/kasan/quarantine.c | 40 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 40 insertions(+)
--
2.18.0
Powered by blists - more mailing lists