[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1554964555.21725.14.camel@suse.com>
Date: Thu, 11 Apr 2019 08:35:55 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Raul E Rangel <rrangel@...omium.org>, linux-usb@...r.kernel.org
Cc: Miquel Raynal <miquel.raynal@...tlin.com>, djkurtz@...omium.org,
Dmitry Torokhov <dtor@...omium.org>, groeck@...omium.org,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Johan Hovold <johan@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Roger Quadros <rogerq@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb/hcd: Send a uevent signaling that the host
controller has died
On Mi, 2019-04-10 at 14:35 -0600, Raul E Rangel wrote:
> This change will send a CHANGE event to udev with the DEAD environment
> variable set when the HC dies. I chose this instead of any of the other
> udev events because it's representing a state change in the host
> controller. The only other event that might have fit was OFFLINE, but
> that seems to be used for hot-removal.
>
> By notifying user space the appropriate policies can be applied.
> e.g.,
> * Collect error logs.
> * Notify the user that USB is no longer functional.
> * Perform a graceful reboot.
Could you please make sure this type of event is shared with other
subsystems whose devices can "die"?
It looks to me like SCSI offline should for example create the
same event. This kind of thing needs to be documented.
Regards
Oliver
Powered by blists - more mailing lists