[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1CA39814-DE67-4112-8F97-D62B9F47FF9D@lca.pw>
Date: Thu, 2 Jan 2020 10:42:51 -0500
From: Qian Cai <cai@....pw>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: tytso@....edu, Arnd Bergmann <arnd@...db.de>,
gregkh@...uxfoundation.org, pmladek@...e.com,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>,
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 Dec 16, 2019, at 8:52 PM, Qian Cai <cai@....pw> wrote:
>
>
>
>> On Dec 4, 2019, at 8:00 PM, Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> wrote:
>>
>> A 'Reviewed-by' will suffice.
>>
>> Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
>
> Ted, could you take a look at this trivial patch?
Not sure if Ted is still interested in maintaining this file as he had no feedback for more
than a month. The problem is that this will render the lockdep useless for a general
debugging tool as it will disable the lockdep early in the process.
Could Andrew (since the free page shuffle will call get_random) or Linus pick this up
directly with the approval from one of the printk() maintainers above?
https://lore.kernel.org/lkml/1573679785-21068-1-git-send-email-cai@lca.pw/
Powered by blists - more mailing lists