[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200527143642.5e4ffba0@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Wed, 27 May 2020 14:36:42 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: jeyu@...nel.org, davem@...emloft.net, michael.chan@...adcom.com,
dchickles@...vell.com, sburla@...vell.com, fmanlunas@...vell.com,
aelior@...vell.com, GR-everest-linux-l2@...vell.com,
kvalo@...eaurora.org, johannes@...solutions.net,
akpm@...ux-foundation.org, arnd@...db.de, rostedt@...dmis.org,
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,
derosier@...il.com, keescook@...omium.org, daniel.vetter@...ll.ch,
will@...nel.org, mchehab+samsung@...nel.org, vkoul@...nel.org,
mchehab+huawei@...nel.org, robh@...nel.org, mhiramat@...nel.org,
sfr@...b.auug.org.au, linux@...inikbrodowski.net,
glider@...gle.com, paulmck@...nel.org, elver@...gle.com,
bauerman@...ux.ibm.com, yamada.masahiro@...ionext.com,
samitolvanen@...gle.com, yzaikin@...gle.com, dvyukov@...gle.com,
rdunlap@...radead.org, corbet@....net, dianders@...omium.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH v3 0/8] kernel: taint when the driver firmware crashes
On Wed, 27 May 2020 03:19:18 +0000 Luis Chamberlain wrote:
> I read your patch, and granted, I will accept I was under the incorrect
> assumption that this can only be used by networking devices, however it
> the devlink approach achieves getting userspace the ability with
> iproute2 devlink util to query a device health, on to which we can peg
> firmware health. But *this* patch series is not about health status and
> letting users query it, its about a *critical* situation which has come up
> with firmware requiring me to reboot my system, and the lack of *any*
> infrastructure in the kernel today to inform userspace about it.
>
> So say we use netlink to report a critical health situation, how are we
> informing userspace with your patch series about requring a reboot?
One of main features of netlink is pub/sub model of notifications.
Whatever you imagine listening to your uevent can listen to
devlink-health notifications via devlink.
In fact I've shown this off in the RFC patches I sent to you, see
the devlink mon health command being used.
Powered by blists - more mailing lists