[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200516040348.GA3182@x1-fbsd>
Date: Sat, 16 May 2020 00:03:48 -0400
From: Rafael Aquini <aquini@...hat.com>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: jeyu@...nel.org, akpm@...ux-foundation.org, arnd@...db.de,
rostedt@...dmis.org, mingo@...hat.com, cai@....pw,
dyoung@...hat.com, bhe@...hat.com, peterz@...radead.org,
tglx@...utronix.de, gpiccoli@...onical.com, pmladek@...e.com,
tiwai@...e.de, schlad@...e.de, andriy.shevchenko@...ux.intel.com,
keescook@...omium.org, daniel.vetter@...ll.ch, will@...nel.org,
mchehab+samsung@...nel.org, kvalo@...eaurora.org,
davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 01/15] taint: add module firmware crash taint support
On Fri, May 15, 2020 at 09:28:32PM +0000, Luis Chamberlain wrote:
> Device driver firmware can crash, and sometimes, this can leave your
> system in a state which makes the device or subsystem completely
> useless. Detecting this by inspecting /proc/sys/kernel/tainted instead
> of scraping some magical words from the kernel log, which is driver
> specific, is much easier. So instead provide a helper which lets drivers
> annotate this.
>
> Once this happens, scrapers can easily look for modules taint flags
> for a firmware crash. This will taint both the kernel and respective
> calling module.
>
> The new helper module_firmware_crashed() uses LOCKDEP_STILL_OK as this
> fact should in no way shape or form affect lockdep. This taint is device
> driver specific.
>
> Signed-off-by: Luis Chamberlain <mcgrof@...nel.org>
> ---
> Documentation/admin-guide/tainted-kernels.rst | 6 ++++++
> include/linux/kernel.h | 3 ++-
> include/linux/module.h | 13 +++++++++++++
> include/trace/events/module.h | 3 ++-
> kernel/module.c | 5 +++--
> kernel/panic.c | 1 +
> tools/debugging/kernel-chktaint | 7 +++++++
> 7 files changed, 34 insertions(+), 4 deletions(-)
>
Reviewed-by: Rafael Aquini <aquini@...hat.com>
Powered by blists - more mailing lists