[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <00116950-7DFB-4F93-959A-06D63E8FF51E@lca.pw>
Date: Thu, 2 Jan 2020 12:16:28 -0500
From: Qian Cai <cai@....pw>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>, tytso@....edu,
Arnd Bergmann <arnd@...db.de>, gregkh@...uxfoundation.org,
pmladek@...e.com, Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, dan.j.williams@...el.com,
Peter Zijlstra <peterz@...radead.org>, longman@...hat.com,
Thomas Gleixner <tglx@...utronix.de>,
Linux-MM <linux-mm@...ck.org>,
linux-arm-kernel@...ts.infradead.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] char/random: silence a lockdep splat with printk()
> On Jan 2, 2020, at 12:07 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> How would this disable lockdep early in the process? The patch is just
> changing pr_notice() to printk_deferred() correct?
Yes, I meant without this patch. Lockdep will easily generate this potential deadlock warning early after boot and then disable itself.
Powered by blists - more mailing lists