linux-kernel - [PATCH 0/2] page_owner: Fixup and cleanup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date: Wed,  6 Mar 2024 13:32:15 +0100
From: Oscar Salvador <osalvador@...e.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org,
	linux-mm@...ck.org,
	Michal Hocko <mhocko@...e.com>,
	Vlastimil Babka <vbabka@...e.cz>,
	Marco Elver <elver@...gle.com>,
	Andrey Konovalov <andreyknvl@...il.com>,
	Alexander Potapenko <glider@...gle.com>,
	Oscar Salvador <osalvador@...e.de>
Subject: [PATCH 0/2] page_owner: Fixup and cleanup

Hi,

this patchset consists of a fixup by an error that was reported by intel
robot, where it seems to be that by the time page_owner gets
initialized, stackdepot has already depleted its allocation space and
returns 0-handles, turning that into null stack_records when trying
to retrieve the stack_record.
I was not able to reproduce that from the config because it booted fine
for me, but when setting e.g: dummy_handle to 0 artificially,
I could see the same error that was reported.

The second patch is a cleanup that can also lead to a compilation
warning.

Oscar Salvador (2):
  mm,page_owner: Check for null stack_record before bumping its refcount
  mm,page_owner: Drop unnecesary check

 mm/page_owner.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

-- 
2.44.0