From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C3A98C433EF for ; Tue, 19 Apr 2022 07:29:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349315AbiDSHb4 (ORCPT ); Tue, 19 Apr 2022 03:31:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53142 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236225AbiDSHby (ORCPT ); Tue, 19 Apr 2022 03:31:54 -0400 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CA217DEA7 for ; Tue, 19 Apr 2022 00:29:12 -0700 (PDT) Received: from canpemm500002.china.huawei.com (unknown [172.30.72.53]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4KjFlb2Tw4zfZ1q; Tue, 19 Apr 2022 15:28:27 +0800 (CST) Received: from [10.174.177.76] (10.174.177.76) by canpemm500002.china.huawei.com (7.192.104.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 19 Apr 2022 15:29:10 +0800 Subject: Re: [PATCH v2] mm/swapfile: unuse_pte can map random data if swap read fails To: Alistair Popple CC: , , , , , , , , , , , , , References: <20220416030549.60559-1-linmiaohe@huawei.com> <87tuapk9n7.fsf@nvdebian.thelocal> From: Miaohe Lin Message-ID: <5a78dd68-343d-ac57-a698-2cfead8ee366@huawei.com> Date: Tue, 19 Apr 2022 15:29:10 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <87tuapk9n7.fsf@nvdebian.thelocal> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.177.76] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To canpemm500002.china.huawei.com (7.192.104.244) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/4/19 11:51, Alistair Popple wrote: > Miaohe Lin writes: > >> 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. > > Hi Miaohe, > > It seems we're not actually using the pfn that gets stored in the special swap > entry here. Is my understanding correct? If so I think it would be better to use Yes, you're right. The pfn is not used now. What we need here is a special swap entry to do the right things. I think we can change to store some debugging information instead of pfn if needed in the future. > the new PTE markers Peter introduced[1] rather than adding another swap entry > type. IIUC, we should not reuse that swap entry here. From definition: PTE markers =========== ... PTE marker is a new type of swap entry that is ony applicable to file backed memories like shmem and hugetlbfs. It's used to persist some pte-level information even if the original present ptes in pgtable are zapped. It's designed for file backed memories while swapin error entry is for anonymous memories. And there has some differences in processing. So it's not a good idea to reuse pte markers. Or am I miss something? > > [1] - Many thanks for your comment and suggestion! :) > ...