Re: percolating ERESTARTSYS beyond PCI subsystem

2015-04-19 Thread Greg KH
On Sun, Apr 19, 2015 at 07:14:26PM +0200, Milton Krutt wrote: > > On Sat, Apr 18, 2015 at 01:40:57PM +0200, Milton Krutt wrote: > > > Hi. The scenario is a PCI driver on a kernel 3.19.2: > > > > > > is it possible, in case pending_signal(current) is true, to return > > > -ERESTARTSYS > > > to in

Re: percolating ERESTARTSYS beyond PCI subsystem

2015-04-19 Thread Milton Krutt
> On Sat, Apr 18, 2015 at 01:40:57PM +0200, Milton Krutt wrote: > > Hi. The scenario is a PCI driver on a kernel 3.19.2: > > > > is it possible, in case pending_signal(current) is true, to return > > -ERESTARTSYS > > to insmod process, in order to get it restart (as expectable)? > > > > After s

Re: percolating ERESTARTSYS beyond PCI subsystem

2015-04-18 Thread Greg KH
On Sat, Apr 18, 2015 at 01:40:57PM +0200, Milton Krutt wrote: > Hi. The scenario is a PCI driver on a kernel 3.19.2: > > is it possible, in case pending_signal(current) is true, to return > -ERESTARTSYS > to insmod process, in order to get it restart (as expectable)? > > After some attempts (wi

percolating ERESTARTSYS beyond PCI subsystem

2015-04-18 Thread Milton Krutt
Hi. The scenario is a PCI driver on a kernel 3.19.2: is it possible, in case pending_signal(current) is true, to return -ERESTARTSYS to insmod process, in order to get it restart (as expectable)? After some attempts (with pending_signal(current) being true), it seems that -ERESTARTSYS is caught