linux-kernel - Re: Fwd: Watchdog detected hard lockup.

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-next>] [day] [month] [year] [list]

Message-ID: <20170525055014.GB386@jagdpanzerIV.localdomain>
Date:   Thu, 25 May 2017 14:50:14 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To:     Sumit Gemini <sumit.gemini0@...il.com>
Cc:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
        Petr Mladek <pmladek@...e.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        linux-kernel@...r.kernel.org
Subject: Re: Fwd: Watchdog detected hard lockup.

On (05/25/17 11:14), Sumit Gemini wrote:
>    Thanks Sergey and i forgot to add other guys in discussion.
>     
> 
>    [1]lkml.kernel.org/r/20170509082859.854-1-sergey.senozhatsky@...il.com
> 
>    Now I'm going for backporting the kernel with RFC, as you suggested me
>    yesterday.

or you can try to reduce the amount of data you printk from IRQ. do you
need to hex dump sbks all the time? switching to a deferred printk won't
do the trick, probably, because you gonna console_unlock() from IRQ in
the worst case anyway.

	-ss