linux-kernel - Re: sched: serial port lockdep warning when offlining CPUs

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

Date:   Thu, 28 Sep 2017 21:15:21 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>,
        Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
        Sasha Levin <levinsasha928@...il.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...e.hu>,
        "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
        "pmladek@...e.com" <pmladek@...e.com>,
        "sergey.senozhatsky@...il.com" <sergey.senozhatsky@...il.com>,
        "rostedt@...dmis.org" <rostedt@...dmis.org>
Subject: Re: sched: serial port lockdep warning when offlining CPUs

On (09/28/17 14:07), Peter Zijlstra wrote:
[..]
> > Nah.. WARN's _should_ not trigger. If they do we fix that.
> > 
> > Getting a lockdep splat after a WARN is something I can live with.
> > 
> > And you really don't want that deferred nonsense for WARNs, because that
> > means you'll risk not over getting the output.
> 
> Note that I'm not likely to care too much either way, because I'm simply
> not using any of that printk() nonsense ;-)
> 
> 
> I'll repost my patches now; otherwise I'll forget again anyway.

#define printk printk_deferred

should also do the trick and... make the kernel great again!  :)

	-ss