lkml.org 
[lkml]   [2018]   [May]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH] userfaultfd: prevent non-cooperative events vs mcopy_atomic races
    From
    Date

    >> But doesn't it race even with regular PF handling, not only the fork? How
    >> do we handle this race?
    >
    > With the regular #PF handing, the faulting thread patiently waits until
    > page fault is resolved. With fork(), mremap() etc the thread that caused
    > the event resumes once the uffd message is read by the monitor. That's
    > surely way before monitor had chance to somehow process that message.

    Ouch, yes. This is nasty :( So having no better solution in mind, let's
    move forward with this.

    Acked-by: Pavel Emelyanov <xemul@virtuozzo.com>

    \
     
     \ /
      Last update: 2018-05-25 16:06    [W:3.224 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site