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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Sep 2017 15:35:36 -0700
From:   Randy Dunlap <>
To:     Sriram V <>,,
        Tejun Heo <>
Subject: Re: Kernel Panic sysrq questions

On 08/18/17 08:40, Sriram V wrote:
> 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.

What kernel version?

I don't see anything in the wq docs about that specific point.



Powered by blists - more mailing lists