linux-kernel - Re: No care given to GDB scripts..

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

Message-Id: <20231129170254.e7ca4c866b521c291e88395e@linux-foundation.org>
Date:   Wed, 29 Nov 2023 17:02:54 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Florian Fainelli <f.fainelli@...il.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Jan Kiszka <jan.kiszka@...mens.com>,
        Kieran Bingham <kbingham@...nel.org>,
        Shanker Donthineni <sdonthineni@...dia.com>,
        Kuan-Ying Lee <Kuan-Ying.Lee@...iatek.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>
Subject: Re: No care given to GDB scripts..

On Wed, 29 Nov 2023 16:23:55 -0800 Florian Fainelli <f.fainelli@...il.com> wrote:

> > Is there any way of scripting the scripts so we can have some sort of
> > automated testing down under tools/testing/selftests/?
> 
> That might be a bit difficult to do as this would mean that we can self 
> debug and introspect using gdb the live kernel. Testing using QEMU is 
> definitively doable however. Of course, I just found another script that 
> broke (device.py)!

Oh.  That sounds quite the exercise in the context of tools/selftests.

One can of course just fire up gdb against the vmlinux elf file and
play around, but I assume this won't permit a useful amount of the
scripts to be exercised.

Suppose someone has set up qemu or whatever and has attached gdb to it.
Could we provide that person with a script or a canned set of commands
which exercise the gdb scripts to a useful extent?  So rather than
attempting automated testing under the seltests umbrella, we provide
less skilled individuals with the means to easily and quickly check for
regressions.  I'd expect that such a toolset would be particularly
helpful for regression testing the scripts across all the supported
architectures?