Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp2795624pxb; Mon, 25 Apr 2022 02:39:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx7vkBg6Uk7ASzn0/XHEhEXyaSWvXtSlsicYlNctPhReqNbdkfhGv5HcTIXwP534aqqN53m X-Received: by 2002:a17:907:c1b:b0:6f0:1335:6fb with SMTP id ga27-20020a1709070c1b00b006f0133506fbmr15737443ejc.294.1650879547776; Mon, 25 Apr 2022 02:39:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650879547; cv=none; d=google.com; s=arc-20160816; b=zgqmwy27+gi2EQ9awbj5FyQY11aH7noF5R6iZI+TH99LwDOi43SY3aCOYMBTY3hH1H SMhZAIgHl+EKByvV0S6z5Ty1FxPisj5VJuG8usdnDmG0Y3qpXVKSLEiGZ3D0ho6uKmXs pk83m/LyScwAlgHQiAtVAcPKkI99/ZHQXi0qazS8O+cJDGARWDh8B3jviCDXry6OJjv3 RiU6UXerrVuOZKlRRkds3k8IsfWkPVvtFW7Ru9GCtASxZcUSmEfecDqsYOJOWfwkV1as AMLKlSwAfgjq/KIBG8othvQdWlPmh7KR48Pk7TeCrJgeZnH5UqPPfBBCdZR+6VlO4EBU KRFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=Y3SbmLM4+sRVv+1OYfDFQVYsSIqnIKC1qx2LcJKv4lw=; b=T+pWmZH6+tm2DwddA83grIS9bHdkYxuKifqsAQZDPJsE3nRlhsP8GRBcvLUMlFS8VO 4HpB3C0UgVQVnIO40s084FbNstJWywz2/4IORqe159ZQ6xCrFcBtnRvjwUj69Cn+XHlK hFuKV0Zu51G+3ox60hwDvF56xxW1UsixvpJVu6An6VV/df4oFGSrQzX7esB33JngWfNq 4P/7aXLq42COmOubLaAC4jBoJEdxqgtOwO/PsdPuTUG/nOhzKHkKL4rUSwRXw64Nd3QJ eOdv9yBYP7m9PJH3Yd7r5N8Hx3iMhYuZY7t9TH2yDoAXlwaNwmVFDJXEn7M42BYjq63Z CCig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=dt4PuQlO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id sb22-20020a1709076d9600b006f37fd71fe2si5039199ejc.387.2022.04.25.02.38.42; Mon, 25 Apr 2022 02:39:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=dt4PuQlO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239899AbiDYHoq (ORCPT + 99 others); Mon, 25 Apr 2022 03:44:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54758 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238882AbiDYHop (ORCPT ); Mon, 25 Apr 2022 03:44:45 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9B48B3BA55 for ; Mon, 25 Apr 2022 00:41:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650872501; x=1682408501; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=ypRaFhfgGoMckctkb+UqL7k4rnajuSRtG45ikgdAanE=; b=dt4PuQlOL5GaZIfy+q2lWWZwL1hGo8v1j0ZmhAjeiPmIi407am1IXxMb K4UBzCoHgDwvlEneMztk+PvyZxMP+z9ob9TiDHKdFvuLy8gKbv2VvtifN eVHyJBORMWQkPVFPrZe3KwjSRmXTAsjfxQfeUt32SvOVmNTgC0jOJ43K7 85NviFrP37mLDFhlD39IYmscSwubW9IBKSmqYrHXHQeAMDVnNLgH3BJik U3i1rU2Fazx6fEpAeYuTHbblJLJyBU+gEgS4R/k1HZJlTsUR+pYt4fdBp g6LnzVMQxIVH3al5HPzL1g9L2HRFHt2E/O8hBCN3AahxeaYwYW6+/Zpc9 g==; X-IronPort-AV: E=McAfee;i="6400,9594,10327"; a="264022261" X-IronPort-AV: E=Sophos;i="5.90,287,1643702400"; d="scan'208";a="264022261" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Apr 2022 00:41:33 -0700 X-IronPort-AV: E=Sophos;i="5.90,287,1643702400"; d="scan'208";a="676565732" Received: from wupeng-mobl.ccr.corp.intel.com ([10.254.215.115]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Apr 2022 00:41:27 -0700 Message-ID: <8aeebc2f0b2a251d3d70402cd0edf063ba911013.camel@intel.com> Subject: Re: [PATCH v3 1/3] mm/swapfile: unuse_pte can map random data if swap read fails From: "ying.huang@intel.com" To: Miaohe Lin , akpm@linux-foundation.org Cc: willy@infradead.org, vbabka@suse.cz, dhowells@redhat.com, neilb@suse.de, david@redhat.com, apopple@nvidia.com, surenb@google.com, minchan@kernel.org, peterx@redhat.com, sfr@canb.auug.org.au, naoya.horiguchi@nec.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Date: Mon, 25 Apr 2022 15:41:25 +0800 In-Reply-To: <20220424091105.48374-2-linmiaohe@huawei.com> References: <20220424091105.48374-1-linmiaohe@huawei.com> <20220424091105.48374-2-linmiaohe@huawei.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.3-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Miaohe, On Sun, 2022-04-24 at 17:11 +0800, Miaohe Lin wrote: > There is a bug in unuse_pte(): when swap page happens to be unreadable, > page filled with random data is mapped into user address space. In case > of error, a special swap entry indicating swap read fails is set to the > page table. So the swapcache page can be freed and the user won't end up > with a permanently mounted swap because a sector is bad. And if the page > is accessed later, the user process will be killed so that corrupted data > is never consumed. On the other hand, if the page is never accessed, the > user won't even notice it. > > Signed-off-by: Miaohe Lin > Acked-by: David Hildenbrand > --- >  include/linux/swap.h | 7 ++++++- >  include/linux/swapops.h | 10 ++++++++++ >  mm/memory.c | 5 ++++- >  mm/swapfile.c | 11 +++++++++++ >  4 files changed, 31 insertions(+), 2 deletions(-) > > diff --git a/include/linux/swap.h b/include/linux/swap.h > index 5553189d0215..b82c196d8867 100644 > --- a/include/linux/swap.h > +++ b/include/linux/swap.h > @@ -55,6 +55,10 @@ static inline int current_is_kswapd(void) >   * actions on faults. >   */ > > +#define SWP_SWAPIN_ERROR_NUM 1 > +#define SWP_SWAPIN_ERROR (MAX_SWAPFILES + SWP_HWPOISON_NUM + \ > + SWP_MIGRATION_NUM + SWP_DEVICE_NUM + \ > + SWP_PTE_MARKER_NUM) > > It appears wasteful to use another swap device number. Is it possible to use a special swap offset? For example, 0 or -1? Best Regards, Huang, Ying [snip]