From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 916E71C3BE0 for ; Mon, 10 Mar 2025 18:50:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741632643; cv=none; b=m4T22vDxXr8lfJldQPrfYTQEUKGtiahKC8eTJ3Mr1bfnhutLGWsKwplZi0emkvmotHknho5TET9tTzCRKvgKyfI2M3kLEfwIm4SV/Wnpzeubi+Y1bAijbRTnNkCrpZJyo8sfmU+VAzWrBsdj11EJWoFZeuji+fu3jeH4NgYcpj8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741632643; c=relaxed/simple; bh=dPX9KXMSSrozDVw+qUXao0MbiQYYiyrdTiOy2wYJvtU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=IV0vdTCgYg0uaX1RWErz4CdhKHlNmacc7aGif/UYQZUV3+9XDGM81BgpMO6BaNFGTdUkVHzYfSSINbd2o2nDmF63bvmkH17i6O1HYPjtYqTNyAyFyEXfcr4MMmACKsWKLqOXXWKkqyUi8J0YHBSpBlBkfbLXF2la0bSl2xlSEnc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=M+dQb5ju; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="M+dQb5ju" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1741632640; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wbs7NSbL6vKlRMHSJIXxZs2mfOWdL12EXaa0cm8bbjU=; b=M+dQb5juiQK8ZspEWopOoHO3GHUh9uBObo/M5O5Nf7EIHx8epbgcR49VpIGrJSegH4//iE FkQF8+yWFQEdJjo6ovHZA4O1lJW2YLBcNJuxcgvGLGvg6ApH8Pu0sb7tRUDvLnSb6+1qZu krwGW0EdcaYZDfHAPyyrCqAQQrvoAbU= Received: from mail-qv1-f69.google.com (mail-qv1-f69.google.com [209.85.219.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-479-oOfdR81MNeG5s_qwTOksrg-1; Mon, 10 Mar 2025 14:50:39 -0400 X-MC-Unique: oOfdR81MNeG5s_qwTOksrg-1 X-Mimecast-MFC-AGG-ID: oOfdR81MNeG5s_qwTOksrg_1741632638 Received: by mail-qv1-f69.google.com with SMTP id 6a1803df08f44-6e8feffbe08so104643326d6.0 for ; Mon, 10 Mar 2025 11:50:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741632638; x=1742237438; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wbs7NSbL6vKlRMHSJIXxZs2mfOWdL12EXaa0cm8bbjU=; b=FtqD0sh5r+roXY96Gf5/P8urW2lyQgjDrkFZ9bCmu19Klw5Pkwd9mLCX37eTX3A3GO mbGnqnIMPl7kWzpNAABlMO5o7kULumnuOfrgXSzNWhxU6kwU1J0EBMhtwsL6IIvqKM0S RWlfe31c/xaBa9YuvWo7K11Z6UXmcT2fgD3Hvih90TfOi+POgqKT5LxzepS8Y3pnNF98 5a8ZJNhe2ZRoyehjQlZep4I5m1goUd0czdF1JFMzRVPfCXglVljeqhdILgEdgb6y5eBd G3cbnHc++7O2XBhH7zcTZP6GbsuJR5LYX0c+2B+XFxtF7i6CqLAfrz+UjAB0krnYfLkV PrqA== X-Forwarded-Encrypted: i=1; AJvYcCVtrnf2W1VsPY6CIe1Jl7INrBUkCu296q5bit/RsrWz6yRCHkIb8n2gAl+iI0idOvrTbZcGdWMBb2dqk7k=@vger.kernel.org X-Gm-Message-State: AOJu0YzKKuCs7DyfD6lMKcavd9IT5o+nYNDpqQn9SJ8ug31jrh7aXCPH VFlURvKpNIZdEB1i/qT9hbdFLjipsD+izbhdp1umwKBDDX64Vyli10NZSUlChKr+kaWjrv1HWLt QarxLI0OEF8nylOqy0iFz8/rGFIBSR6ab6StbOmzl3zDmOZrrHyUb77PqPpc5zg== X-Gm-Gg: ASbGncsuYx7+FmjFFkFsflwkFJfIiHe4xvb3I7zj5h+fjU3RKVY8eC29y5ZLlCFFrdE HptDq4bIuAFXwx46otbGB5RIbreCYCKjT7kk0+AQIz2HyoJy8752uO6YWNMhQ7B6IpwXnc4rBgZ IeI7k07zv0F9oBsKMxb30TV3FEQC6pxrMhD0KHsTBzzFF0qEMoU5c9PHsT10G0hgmk807qhq+tz UcFvre9KDwlCtG4ITctqgHDOgTj3Du5uhremQEQah1NFleAzD+Q9u6jQCNuRqLIp7PQrtTFmAmB M9SGGQo= X-Received: by 2002:a05:6214:21cb:b0:6e8:9fcb:5f7d with SMTP id 6a1803df08f44-6e9006913cdmr229708396d6.36.1741632638608; Mon, 10 Mar 2025 11:50:38 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFie+mzm2Bw8VvHKP/u+MGW8Iw61YPMj501OCpii1PEfvhFOD2xnDZkzVVnlM30dQ3KOy/+cA== X-Received: by 2002:a05:6214:21cb:b0:6e8:9fcb:5f7d with SMTP id 6a1803df08f44-6e9006913cdmr229708106d6.36.1741632638222; Mon, 10 Mar 2025 11:50:38 -0700 (PDT) Received: from x1.local ([85.131.185.92]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6e8f7170958sm61093186d6.108.2025.03.10.11.50.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Mar 2025 11:50:37 -0700 (PDT) Date: Mon, 10 Mar 2025 14:50:34 -0400 From: Peter Xu To: Jinjiang Tu Cc: jimsiak , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk, linux-mm@kvack.org, wangkefeng.wang@huawei.com Subject: Re: Using userfaultfd with KVM's async page fault handling causes processes to hung waiting for mmap_lock to be released Message-ID: References: <79375b71-db2e-3e66-346b-254c90d915e2@cslab.ece.ntua.gr> <20250307072133.3522652-1-tujinjiang@huawei.com> <46ac83f7-d3e0-b667-7352-d853938c9fc9@huawei.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Mon, Mar 10, 2025 at 02:40:35PM +0800, Jinjiang Tu wrote: > > 在 2025/3/8 6:41, Peter Xu 写道: > > On Fri, Mar 07, 2025 at 03:11:09PM +0200, jimsiak wrote: > > > Hi, > > > > > > From my side, I managed to avoid the freezing of processes with the > > > following change in function userfaultfd_release() in file fs/userfaultfd.c > > > (https://elixir.bootlin.com/linux/v5.13/source/fs/userfaultfd.c#L842): > > > > > > I moved the following command from line 851: > > > WRITE_ONCE(ctx->released, true); > > > (https://elixir.bootlin.com/linux/v5.13/source/fs/userfaultfd.c#L851) > > > > > > to line 905, that is exactly before the functions returns 0. > > > > > > That simple workaround worked for my use case but I am far from sure that is > > > a correct/sufficient fix for the problem at hand. > > Updating the field after userfaultfd_ctx_put() might mean UAF, afaict. > > > > Maybe it's possible to remove ctx->released but only rely on the mmap write > > lock. However that'll need some closer look and more thoughts. > > > > To me, the more straightforward way to fix it is to use the patch I > > mentioned in the other email: > > > > https://lore.kernel.org/all/ZLmT3BfcmltfFvbq@x1n/ > > > > Or does it mean it didn't work at all? > > This patch works for me. mlock() syscall calls GUP with FOLL_UNLOCKABLE and > allows to release mmap lock and retry. > > But other GUP call without FOLL_UNLOCKABLE will return VM_FAULT_SIGBUS, > is it a regression for the below commit？ Do you have an explicit reproducer / use case of such? AFAIU, below commit should only change it from SIGBUS to NOPAGE when "released" is set. I don't see how it can regress on !FOLL_UNLOCKABLE. Thanks, > > commit 656710a60e3693911bee3a355d2f2bbae3faba33 > Author: Andrea Arcangeli > Date: Fri Sep 8 16:12:42 2017 -0700 > > userfaultfd: non-cooperative: closing the uffd without triggering SIGBUS > > > > > Thanks, > > > -- Peter Xu