[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200511152141.2305e916@gandalf.local.home>
Date: Mon, 11 May 2020 15:21:41 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shannon Nelson <snelson@...sando.io>
Cc: Luis Chamberlain <mcgrof@...nel.org>, jeyu@...nel.org,
akpm@...ux-foundation.org, arnd@...db.de, mingo@...hat.com,
aquini@...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 00/15] net: taint when the device driver firmware
crashes
On Sat, 9 May 2020 18:01:51 -0700
Shannon Nelson <snelson@...sando.io> wrote:
> If the driver is able to detect that the device firmware has come back
> alive, through user intervention or whatever, should there be a way to
> "untaint" the kernel? Or would you expect it to remain tainted?
The only way to untaint a kernel is a reboot. A taint just means "something
happened to this kernel since it was booted". It's used as a hint, and
that's all.
I agree with the other comments in this thread. Use devlink health or
whatever tool to look further into causes. But from what I see here, this
code is "good enough" for a taint.
-- Steve
Powered by blists - more mailing lists