lkml.org 
[lkml]   [2016]   [Mar]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 0/12] introduce down_write_killable for rw_semaphore

* Michal Hocko <mhocko@kernel.org> 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

\
 
 \ /
  Last update: 2016-03-10 12:01    [W:0.072 / U:0.508 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site