Re: [PATCH] autofs4: Fix endless loop in autofs4_write

2016-06-10 Thread Ian Kent
On Sat, 2016-06-11 at 09:09 +0800, Ian Kent wrote: > On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote: > > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the > > check done on the __vfs_write()'s returned value in autofs4_write(). > > This may lead to a spinning process

Re: [PATCH] autofs4: Fix endless loop in autofs4_write

2016-06-10 Thread Ian Kent
On Sat, 2016-06-11 at 09:09 +0800, Ian Kent wrote: > On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote: > > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the > > check done on the __vfs_write()'s returned value in autofs4_write(). > > This may lead to a spinning process

Re: [PATCH] autofs4: Fix endless loop in autofs4_write

2016-06-10 Thread Ian Kent
On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote: > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the > check done on the __vfs_write()'s returned value in autofs4_write(). > This may lead to a spinning process which can't catch any signal. Yeah, sorry my bad. > >

Re: [PATCH] autofs4: Fix endless loop in autofs4_write

2016-06-10 Thread Ian Kent
On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote: > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the > check done on the __vfs_write()'s returned value in autofs4_write(). > This may lead to a spinning process which can't catch any signal. Yeah, sorry my bad. > >

[PATCH] autofs4: Fix endless loop in autofs4_write

2016-06-10 Thread Laurent Dufour
The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the check done on the __vfs_write()'s returned value in autofs4_write(). This may lead to a spinning process which can't catch any signal. Call stack showed in xmon could be : [c003a76c7500] c030df74

[PATCH] autofs4: Fix endless loop in autofs4_write

2016-06-10 Thread Laurent Dufour
The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the check done on the __vfs_write()'s returned value in autofs4_write(). This may lead to a spinning process which can't catch any signal. Call stack showed in xmon could be : [c003a76c7500] c030df74