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-next>] [day] [month] [year] [list]
Message-ID: <CAH9_wRPOnUNQQS9-m0nGpp22wTwPkJXBQ_iOTUvqoqDt_WqMJA@mail.gmail.com>
Date:   Fri, 18 Aug 2017 21:10:25 +0530
From:   Sriram V <vshrirama@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Kernel Panic sysrq questions

Hi,

1. I am testing my watchdog driver. The driver uses the internal
watchdog (Internal to SOC).
2. I use a single core SOC.
3. I have a workqueue which pets the watchdog every 60 seconds.
4. I trigger a kernel crash by doing a echo c > /proc/sysrq-trigger to
trigger  a kernel crash
5. Even after the crash, I observe that the workqueue gets
periodically executed. (I have a printk
    inside the workqueue before the pet as a result the watchdog does
not reset the board.

My Understanding is When a fatal panic happens, The Kernel is in
frozen state (no workques
or tasks get executed).

Is my understanding correct or am i missing something here.


Thanks,

Regards,
Sriram

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ