Re: manipulating sigmask from filesystems and drivers

From: David Woodhouse (
Date: Thu Aug 01 2002 - 17:50:11 EST said:
> It's not the kernel side that is not restartable. It's the _user_
> side.

As I said, you can't allow it to be interrupted after you've started the
copy_to_user(). Show me how the userspace program can prove the signal
arrived _after_ the 'int 0x80' had trapped into the kernel rather then
beforehand, and I'll accept that you can't allow read() to be interrupted
even before the copy_to_user() starts.

But I also agree that there are other, better, examples of why
TASK_UNINTERRUPTIBLE has to be used sometimes. Page faults in
copy_{from,to}_user are probably one such.

It's just that it doesn't have to be scattered all over the place just
because people are too lazy to do the cleanup code.

Yeah -- sometimes it's hard. So go shopping.


- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to More majordomo info at Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:17 EST