[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871szagtls.fsf@xmission.com>
Date: Fri, 21 Oct 2016 00:26:55 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: David Miller <davem@...emloft.net>
Cc: f.fainelli@...il.com, netdev@...r.kernel.org,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
sfr@...b.auug.org.au
Subject: Re: [PATCH] kexec: Export kexec_in_progress to modules
David Miller <davem@...emloft.net> writes:
> From: Florian Fainelli <f.fainelli@...il.com>
> Date: Thu, 20 Oct 2016 18:15:16 -0700
>
>> The bcm_sf2 driver uses kexec_in_progress to know whether it can power
>> down an integrated PHY during shutdown, and can be built as a module.
>> Other modules may be using this in the future, so export it.
>>
>> Fixes: 2399d6143f85 ("net: dsa: bcm_sf2: Prevent GPHY shutdown for kexec'd kernels")
>> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
>> ---
>> Eric, David, Stephen,
>>
>> The offending commit is in David's net.git tree, so it would probably make
>> sense to route the fix through the same tree.
>
> Ok, I'll apply this, thanks Florian.
Florian
I am completely confused why any driver would want to do this.
A reboot is semantically identical to a kexec restart. Always has been.
That is pwoering down your hardware during reboot is not safe.
The only thing that might save you is the hardware reset line being
toggled at which point your hardware is powered up again anyway.
So as far as I can tell you are advocating for a change to support a
driver doing something that is completely pointless. So no let's not
export this symbol. Please fix the driver to do something less
pointless instead.
Eric
Powered by blists - more mailing lists