From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751344AbdBAGfT (ORCPT ); Wed, 1 Feb 2017 01:35:19 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:57848 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750991AbdBAGfS (ORCPT ); Wed, 1 Feb 2017 01:35:18 -0500 Date: Wed, 1 Feb 2017 08:35:07 +0200 From: Mike Rapoport To: Andrew Morton Cc: Andrea Arcangeli , "Dr. David Alan Gilbert" , Hillf Danton , Mike Kravetz , Pavel Emelyanov , Linux-MM , LKML Subject: Re: [PATCH v2 3/5] userfaultfd: non-cooperative: add event for exit() notification References: <1485542673-24387-1-git-send-email-rppt@linux.vnet.ibm.com> <1485542673-24387-4-git-send-email-rppt@linux.vnet.ibm.com> <20170131164132.439f9d30e3a9b3c79bcada3a@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170131164132.439f9d30e3a9b3c79bcada3a@linux-foundation.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 17020106-0020-0000-0000-000002FDB867 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17020106-0021-0000-0000-0000403C3F9D Message-Id: <20170201063506.GA7921@rapoport-lnx> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-01-31_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702010064 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 31, 2017 at 04:41:32PM -0800, Andrew Morton wrote: > On Fri, 27 Jan 2017 20:44:31 +0200 Mike Rapoport wrote: > > > Allow userfaultfd monitor track termination of the processes that have > > memory backed by the uffd. > > > > --- a/fs/userfaultfd.c > > +++ b/fs/userfaultfd.c > > @@ -774,6 +774,30 @@ void userfaultfd_unmap_complete(struct mm_struct *mm, struct list_head *uf) > > } > > } > > > > +void userfaultfd_exit(struct mm_struct *mm) > > +{ > > + struct vm_area_struct *vma = mm->mmap; > > + > > + while (vma) { > > + struct userfaultfd_ctx *ctx = vma->vm_userfaultfd_ctx.ctx; > > + > > + if (ctx && (ctx->features & UFFD_FEATURE_EVENT_EXIT)) { > > + struct userfaultfd_wait_queue ewq; > > + > > + userfaultfd_ctx_get(ctx); > > + > > + msg_init(&ewq.msg); > > + ewq.msg.event = UFFD_EVENT_EXIT; > > + > > + userfaultfd_event_wait_completion(ctx, &ewq); > > + > > + ctx->features &= ~UFFD_FEATURE_EVENT_EXIT; > > + } > > + > > + vma = vma->vm_next; > > + } > > +} > > And we can do the vma walk without locking because the caller (exit_mm) > knows it now has exclusive access. Worth a comment? Sure, will add. Do you prefer an incremental patch or update this one? -- Sincerely yours, Mike.