Re: filesystem signal handling

[David Woodhouse <dwmw2@infradead.org>]

On Wed, 2004-04-28 at 20:28 +0100, Jamie Lokier wrote:
> Trond Myklebust wrote:
> > As for SIGINT vs SIGKILL - the only difference I can see is that the
> > former can be generated directly from the keyboard.
> 
> The other difference is that SIGINT can be intercepted by the
> application to do cleanups or whatever; SIGKILL cannot.

That was the difference I was thinking of -- since if they're not
_handled_, all three of the mentioned signals remain fatal and hence the
resulting behaviour is basically the same with either implementation.
(playing with the mask vs. allowing only fatal signals).

It's the case of a handled SIGINT during NFS operations which is
potentially different. If that happens when a read() or write() is
partially complete, what do we currently do? Is it really mandatory that
we do handle the signal immediately rather than upon completion of the
operation, or is this a corner case which nobody cares about?

But I wasn't necessarily suggesting that NFS should change its
behaviour, only offering a potential answer to the question which was
posed, which was presumably for CIFS not NFS.

-- 
dwmw2