Messages in this thread | | | From | Alex Belits <> | Subject | Re: [PATCH v3 04/13] task_isolation: userspace hard isolation from kernel | Date | Sun, 19 Apr 2020 05:07:41 +0000 |
| |
On Thu, 2020-04-09 at 11:00 -0700, Andy Lutomirski wrote: > > > > > Once the task has returned to userspace after issuing the prctl(), > > if it enters the kernel again via system call, page fault, or any > > other exception or irq, the kernel will kill it with SIGKILL. > > I could easily imagine myself using task isolation, but not with the > SIGKILL semantics. SIGKILL causes data loss. Please at least let > users choose what signal to send.
This is already done, even though the documentation is not updated. There is even a userspace library that deals with this while compensating for possible race conditions on isolation entry and automatic re-entry after isolation is broken: https://github.com/abelits/libtmc
-- Alex
| |