Thread (21 messages) 21 messages, 7 authors, 2017-06-09

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

From: Andy Lutomirski <hidden>
Date: 2017-06-07 04:57:09
Also in: linux-fsdevel, lkml

Possibly related (same subject, not in this thread)

On Tue, Jun 6, 2017 at 5:22 PM, Luis R. Rodriguez [off-list ref] wrote:
On Tue, Jun 06, 2017 at 06:11:51PM -0400, Theodore Ts'o wrote:
quoted
On Tue, Jun 06, 2017 at 06:47:34PM +0200, Luis R. Rodriguez wrote:
quoted
On Tue, Jun 06, 2017 at 03:53:16PM +0100, Alan Cox wrote:
We rely on swait, and swait right now only uses -ERESTARTSYS. Are
you saying we could mask out -ERESTARTSYS and map it to -ERESTARTNOINTR
or -ERESTARTNOHAND if we see fit for some future functionality / need ?
I think that has essentially nothing to do with swait.  User code does
some syscall.  That syscall triggers a firmware load.  The caller gets
a signal.  If you're going to let firmware load get interrupted, you
need to consider what the syscall is.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help