From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f198.google.com (mail-qk0-f198.google.com [209.85.220.198]) by kanga.kvack.org (Postfix) with ESMTP id A8D086B0603 for ; Mon, 31 Jul 2017 09:32:50 -0400 (EDT) Received: by mail-qk0-f198.google.com with SMTP id o124so123786169qke.9 for ; Mon, 31 Jul 2017 06:32:50 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTPS id y25si18234203qtc.18.2017.07.31.06.32.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 06:32:50 -0700 (PDT) Date: Mon, 31 Jul 2017 15:32:47 +0200 From: Andrea Arcangeli Subject: Re: [PATCH] userfaultfd_zeropage: return -ENOSPC in case mm has gone Message-ID: <20170731133247.GK29716@redhat.com> References: <1501136819-21857-1-git-send-email-rppt@linux.vnet.ibm.com> <20170731122204.GB4878@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170731122204.GB4878@dhcp22.suse.cz> Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Mike Rapoport , Andrew Morton , "Dr. David Alan Gilbert" , Pavel Emelyanov , linux-mm , lkml , stable@vger.kernel.org On Mon, Jul 31, 2017 at 02:22:04PM +0200, Michal Hocko wrote: > On Thu 27-07-17 09:26:59, Mike Rapoport wrote: > > In the non-cooperative userfaultfd case, the process exit may race with > > outstanding mcopy_atomic called by the uffd monitor. Returning -ENOSPC > > instead of -EINVAL when mm is already gone will allow uffd monitor to > > distinguish this case from other error conditions. > > Normally we tend to return ESRCH in such case. ENOSPC sounds rather > confusing... This is in sync and consistent with the retval for UFFDIO_COPY upstream: if (mmget_not_zero(ctx->mm)) { ret = mcopy_atomic(ctx->mm, uffdio_copy.dst, uffdio_copy.src, uffdio_copy.len); mmput(ctx->mm); } else { return -ENOSPC; } If you preferred ESRCH I certainly wouldn't have been against, but we should have discussed it before it was upstream. All it matters is it's documented in the great manpage that was written for it as quoted below. +.TP +.B ENOENT +(Since Linux 4.11) +The faulting process has changed +its virtual memory layout simultaneously with outstanding +.I UFFDIO_COPY +operation. +.TP +.B ENOSPC +(Since Linux 4.11) +The faulting process has exited at the time of +.I UFFDIO_COPY +operation. To change it now, we would need to involve manpage and other code changes. Thanks, Andrea -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org