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>] [day] [month] [year] [list]
Date:   Tue, 20 Feb 2018 16:26:14 +0530
From:   Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
To:     linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Cc:     akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
        davem@...emloft.net, ganeshgr@...lsio.com, nirranjan@...lsio.com,
        indranil@...lsio.com, rahul.lakkireddy@...lsio.com
Subject: Appending firmware/hardware dump to vmcore during kernel panic

Hi all,

We have a requirement to collect firmware/hardware state of the
underlying NIC during kernel panic.  We are doing this in cxgb4
driver, using panic notifier list [1].  cxgb4 registers a callback
function to the panic notifier list, which gets invoked during kernel
panic. In the callback function, firmware/hardware dump is collected
into pre-allocated buffer and then extracted later from the vmcore,
for post-analysis.

Is this approach of using panic notifier correct?  Any suggestions are
much appreciated.

Thanks,
Rahul

[1] https://patchwork.ozlabs.org/patch/873830/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ