Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

From: Ingo Molnar
Date: Thu Mar 10 2016 - 05:24:23 EST



* Michal Hocko <mhocko@xxxxxxxxxx> wrote:

> > > Why? Each syscall already is killable as the task might be killed by the OOM
> > > killer.
> >
> > Not all syscalls are interruptible - for example sys_sync() isn't:
>
> I guess we are talking past each other. [...]

Heh, you are being polite, I think what happened is that I was being dense and
didn't understand your point:

> [...] What I meant was that while all syscalls are allowed to not return to the
> userspace because the task might get killed but not all of them accept to get
> interrupted by a signal and return with EINTR. None of the man page of mmap,
> mremap, mlock, mprotect list EINTR as a possibility so I would be really afraid
> of returning an unexpected error code.

Indeed.

> Does this make more sense now?

It does!

Thanks,

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html