linux-kernel - [PATCH 0/3] scripts/gdb/symbols: determine KASLR offset on s390 during early boot

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20250515155811.114392-1-iii@linux.ibm.com>
Date: Thu, 15 May 2025 17:52:10 +0200
From: Ilya Leoshkevich <iii@...ux.ibm.com>
To: Jan Kiszka <jan.kiszka@...mens.com>, Kieran Bingham <kbingham@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, Heiko Carstens <hca@...ux.ibm.com>,
        Vasily Gorbik <gor@...ux.ibm.com>,
        Alexander Gordeev <agordeev@...ux.ibm.com>,
        Ilya Leoshkevich <iii@...ux.ibm.com>
Subject: [PATCH 0/3] scripts/gdb/symbols: determine KASLR offset on s390 during early boot

Hi,

I noticed that debugging s390 early boot using the support I introduced
in commit 28939c3e9925 ("scripts/gdb/symbols: determine KASLR offset on
s390") does not work.

The reason is that decompressor does not provide the vmcoreinfo note,
so KASLR offset needs to be extracted in a different way, which this
series implements. Patches 1-2 are trivial refactorings, and patch 3 is
the implementation.

Best regards,
Ilya

Ilya Leoshkevich (3):
  scripts/gdb/symbols: factor out get_vmlinux()
  scripts/gdb/symbols: factor out pagination_off()
  scripts/gdb/symbols: determine KASLR offset on s390 during early boot

 scripts/gdb/linux/symbols.py | 38 +++++++++++++++++++-----------------
 scripts/gdb/linux/utils.py   | 20 +++++++++++++++++++
 2 files changed, 40 insertions(+), 18 deletions(-)

-- 
2.49.0