linux-kernel - Re: [PATCH v1] regmap: introduce value tracing for regmap bulk operations

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]

Date:   Fri, 19 Aug 2022 15:25:44 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Dmitry Rokosov <DDRokosov@...rdevices.ru>,
        gregkh@...uxfoundation.org, rafael@...nel.org, jic23@...nel.org,
        "linux@...musvillemoes.dk>" <linux@...musvillemoes.dk>,
        tglx@...utronix.de, andy.shevchenko@...il.com,
        kernel <kernel@...rdevices.ru>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] regmap: introduce value tracing for regmap bulk
 operations

On 2022-08-18 16:43, Mark Brown wrote:
> On Thu, Aug 18, 2022 at 02:49:20PM +0100, Marc Zyngier wrote:
> 
>> I don't care much about regmap as a MMIO backend, but it strikes me as
>> odd that you end up with multiple ways of logging the same stuff (with
>> a memcpy in the middle of it).
> 
>> Why can't this be done with a small amount of trace post-processing?
> 
> At the minute we don't put the actual data for the bulk transfers into
> the trace so the information simply isn't there.

But isn't that what this patch should do?

We also have recently merged the CONFIG_TRACE_MMIO_ACCESS which
already dumps all sort of MMIO crap^Winformation.

Surely there should be a more common approach to this.

         M.
-- 
Jazz is not dead. It just smells funny...