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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 31 Jul 2020 22:24:17 -0700
From:   Florian Fainelli <>
To:     Rakesh Pillai <>,
Subject: Re: [PATCH v2 0/3]

On 7/31/2020 10:10 PM, Rakesh Pillai wrote:
>> -----Original Message-----
>> From: Florian Fainelli <>
>> Sent: Saturday, August 1, 2020 12:17 AM
>> To: Rakesh Pillai <>;
>> Cc:;;
>> Subject: Re: [PATCH v2 0/3]
>> On 7/31/20 11:27 AM, Rakesh Pillai wrote:
>>> The history recording will be compiled only if
>>> ATH10K_DEBUG is enabled, and also enabled via
>>> the module parameter. Once the history recording
>>> is enabled via module parameter, it can be enabled
>>> or disabled runtime via debugfs.
>> Why not use trace prints and retrieving them via the function tracer?
>> This seems very ad-hoc.
> Tracing needs to be enabled to capture the events.
> But these events can be turned on in some kind of a debug build and capture the history to help us debug in case there is a crash.
> It wont even allocate memory if not enabled via module parameter.

I would suggest researching what other drivers do and also considering
the benefits, for someone doing system analysis of plugging into the
kernel's general tracing mechanism to have all information in the same
place and just do filtering on the record/report side.

Powered by blists - more mailing lists