linux-kernel - Re: [PATCH] tools/drgn: Add script to display page state for a given PID and VADDR

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <098e977c-55cd-498b-bd36-725333c06210@dorminy.me>
Date: Tue, 15 Apr 2025 23:28:41 -0400
From: Sweet Tea Dorminy <sweettea-kernel@...miny.me>
To: Ye Liu <ye.liu@...ux.dev>, Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-toolchains@...r.kernel.org,
 linux-mm@...ck.org, Ye Liu <liuye@...inos.cn>,
 Omar Sandoval <osandov@...ndov.com>
Subject: Re: [PATCH] tools/drgn: Add script to display page state for a given
 PID and VADDR



On 4/15/25 10:46 PM, Ye Liu wrote:
> 
> 在 2025/4/16 10:14, Andrew Morton 写道:
>> On Tue, 15 Apr 2025 15:50:24 +0800 Ye Liu <ye.liu@...ux.dev> wrote:
>>
>>> From: Ye Liu <liuye@...inos.cn>
>>>
>>> Introduces a new drgn script, `show_page_info.py`, which allows users
>>> to analyze the state of a page given a process ID (PID) and a virtual
>>> address (VADDR). This can help kernel developers or debuggers easily
>>> inspect page-related information in a live kernel or vmcore.
>>>
>>> The script extracts information such as the page flags, mapping, and
>>> other metadata relevant to diagnosing memory issues.
>>>
>>> Currently, there is no specific maintainer entry for `tools/drgn/` in the
>>> MAINTAINERS file. Therefore, this patch is sent to the general kernel and
>>> tools mailing lists for review.
>> Help.  My copy of linux has no tools/drgn/
> I noticed that the current upstream Linux tree doesn't contain a
> `tools/drgn/` directory.
> 
> I'm interested in contributing a drgn script tool as well.
> Given that this directory does not yet exist in mainline, where would
> be the appropriate place to add new drgn scripts? Would it make sense
> to create a new `tools/drgn/` directory, or is there a preferred
> location for such debugging scripts?
> 
> Thanks,
> Ye

I believe the traditional thing to do with new drgn scripts is to add 
them to the contrib directory in drgn via pull request:
https://github.com/osandov/drgn/blob/main/contrib/README.rst