Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: [PATCH] char/random: silence a lockdep splat with printk()
Date:   Thu, 2 Jan 2020 12:16:28 -0500
Message-Id: <00116950-7DFB-4F93-959A-06D63E8FF51E@lca.pw>
References: <20200102120752.7b893b1e@gandalf.local.home>
Cc:     Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>, tytso@mit.edu,
        Arnd Bergmann <arnd@arndb.de>, gregkh@linuxfoundation.org,
        pmladek@suse.com, Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will@kernel.org>, dan.j.williams@intel.com,
        Peter Zijlstra <peterz@infradead.org>, longman@redhat.com,
        Thomas Gleixner <tglx@linutronix.de>,
        Linux-MM <linux-mm@kvack.org>,
        linux-arm-kernel@lists.infradead.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <20200102120752.7b893b1e@gandalf.local.home>
To:     Steven Rostedt <rostedt@goodmis.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Jan 2, 2020, at 12:07 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>=20
> 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.=