[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170717140007.GA12884@kroah.com>
Date: Mon, 17 Jul 2017 16:00:07 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: wagi@...om.org, yi1.li@...ux.intel.com, takahiro.akashi@...aro.org,
luto@...nel.org, ebiederm@...ssion.com, dmitry.torokhov@...il.com,
arend.vanspriel@...adcom.com, dwmw2@...radead.org,
rjw@...ysocki.net, atull@...nel.org, moritz.fischer@...us.com,
pmladek@...e.com, johannes.berg@...el.com,
emmanuel.grumbach@...el.com, luciano.coelho@...el.com,
kvalo@...eaurora.org, torvalds@...ux-foundation.org,
keescook@...omium.org, dhowells@...hat.com, pjones@...hat.com,
hdegoede@...hat.com, alan@...ux.intel.com, tytso@....edu,
dave@...olabs.net, mawilcox@...rosoft.com, tglx@...utronix.de,
peterz@...radead.org, mfuzzey@...keon.com,
jakub.kicinski@...ronome.com, nbroeking@...com,
jewalt@...innovations.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 4/4] firmware: send -EINTR on signal abort on fallback
mechanism
On Thu, Jun 29, 2017 at 01:51:51PM -0700, Luis R. Rodriguez wrote:
> Right now we send -EAGAIN to a syfs write which got interrupted.
> Userspace can't tell what happened though, send -EINTR if we
> were killed due to a signal so userspace can tell things apart.
>
> This is only applicable to the fallback mechanism.
>
> Reported-by: Martin Fuzzey <mfuzzey@...keon.com>
> Signed-off-by: Luis R. Rodriguez <mcgrof@...nel.org>
> ---
> drivers/base/firmware_class.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
This doesn't need to go into 4.13-final, right? Can it wait for
4.14-rc1?
thanks,
greg k-h
Powered by blists - more mailing lists