From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from szxga07-in.huawei.com (szxga07-in.huawei.com [45.249.212.35]) (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 6B0961A3162; Fri, 7 Mar 2025 07:49:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.35 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741333777; cv=none; b=a0Hf0EA0lp73xmDpz+KwmKKY3hLwmmPEx9qx5X+SGCTbAlq0+2rwvRmgoYfoHV1ZKMdxU5SsOJurzI3dSSYeYn6WqtA0d8MvgnKMI4nfhPKQ5+IUZxs4i4oRULTNN5PeBuQwIC6gXWXB0m0LBp613GWhKZMRe9oiKCR3veHzHzY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741333777; c=relaxed/simple; bh=e4b+fg10IcozqcfdM2KBPWzq3EXrk64Clu2Pv7/NkTw=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=rtYxUIdLmhliSWVAA9ELDL1KcEtIlTDYG2Eyb7eefrrxYoafTIfN/u4MNAkpY6h5vpfVyXRo2zQ4NZa0CYJsmMswTsv8lQbcWJyP9Ly7VjxVx37DwqjXGy9EaaTUY7cBb7sVitkjtLxuz7dXBqlCx5BjPOXY8TSyKHG895YVeVw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=45.249.212.35 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.19.162.112]) by szxga07-in.huawei.com (SkyGuard) with ESMTP id 4Z8Hrl2m3Rz1f0Cq; Fri, 7 Mar 2025 15:25:59 +0800 (CST) Received: from kwepemo200002.china.huawei.com (unknown [7.202.195.209]) by mail.maildlp.com (Postfix) with ESMTPS id E8AA01402CE; Fri, 7 Mar 2025 15:30:14 +0800 (CST) Received: from huawei.com (10.175.124.71) by kwepemo200002.china.huawei.com (7.202.195.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 7 Mar 2025 15:30:14 +0800 From: Jinjiang Tu To: CC: , , , , , Subject: Re: Using userfaultfd with KVM's async page fault handling causes processes to hung waiting for mmap_lock to be released Date: Fri, 7 Mar 2025 15:21:33 +0800 Message-ID: <20250307072133.3522652-1-tujinjiang@huawei.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <79375b71-db2e-3e66-346b-254c90d915e2@cslab.ece.ntua.gr> References: <79375b71-db2e-3e66-346b-254c90d915e2@cslab.ece.ntua.gr> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-ClientProxiedBy: dggems701-chm.china.huawei.com (10.3.19.178) To kwepemo200002.china.huawei.com (7.202.195.209) Hi, I encountered the same issue too. In my scenario, GUP is called by mlockall() syscall. Is there a solution to fix it? Thanks.