Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3585123pxf; Mon, 29 Mar 2021 06:21:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz1bxIGLmpNOXX+m3bjrPEpOXlqEhEKyAcURyXCoiIEIHW5xCRSd5KF3nz8BIFihwY6kY9o X-Received: by 2002:a50:fd15:: with SMTP id i21mr27745852eds.384.1617024067199; Mon, 29 Mar 2021 06:21:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617024067; cv=none; d=google.com; s=arc-20160816; b=T9Yww4IIFpGVA52L0nUdy6TKL7XhMT4T9YbtsZFz0MRp3Fa1BgU6oHTECLg8C8/MGx Kz67BOO0/gx9R2IO2I0rkt2kLt3Se48ARKJzf/9HLYQVX8vnNNk+XM3Qf4oMUSheDM2j sykuf9ESm37jH4GFTDNdvZyPQxJeqNBEOQgL2tmg5riVMp3QN07G+S6rcwfFHzTFvm+x dZNQ8UofODf4hRbh1mHSW1ughGqqj1RMilnuZ48JKUAPVCaxaP8zSyXLzmmKf4CfmI1C Q1QptpLosh2Zf0AAfDAf7Z4uphIjV/fC6AOLYInSw/KGJ/uslx+00UybT6EbCsV8rtHZ TjVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :mime-version:user-agent:date:message-id:cc:to:subject:from; bh=Uiw4f0NeCCZItVOjb1Rdk1AFyhIcUZmJ8b6YL+Uez18=; b=SFhYRdvxnE2Pfnxz35lQsHIO60pbhKGyIiKSBC8Nxy7CZSvWqh87UMrzdP7hkw+gkK Od+kQS8e4lkrnWoYSCYQQFW8SFEOjV8qQTIEcYVWk5d14ELH4Px8MfGHzsIgYI93/hZS 9tz/xtgmLZWz8CZT7zPe73p9A5+AmksCGTTESOaPktpdMZ+vbQrv2SCrsAg0YqYgYKvw knhucFieoHWiPY5KC3qopgFQ0UtRTY2Mr0PDQJSVHVb+8mCynH4ya7bhbYDaCXzSNnqM wXVcHvojJ0IEKlfhB66A/DCPacmhVtsYMEaFQpdDE9ZIVrb/cdPBtHoAOHo/EB4TTO6c ooaw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m4si13223948edc.119.2021.03.29.06.20.44; Mon, 29 Mar 2021 06:21:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229910AbhC2NSs (ORCPT + 99 others); Mon, 29 Mar 2021 09:18:48 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:15383 "EHLO szxga06-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229479AbhC2NS1 (ORCPT ); Mon, 29 Mar 2021 09:18:27 -0400 Received: from DGGEMS405-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4F8ClY19r6zlVrV; Mon, 29 Mar 2021 21:16:41 +0800 (CST) Received: from [10.174.179.86] (10.174.179.86) by DGGEMS405-HUB.china.huawei.com (10.3.19.205) with Microsoft SMTP Server id 14.3.498.0; Mon, 29 Mar 2021 21:18:21 +0800 From: Miaohe Lin Subject: [Question] Is there a race window between swapoff vs synchronous swap_readpage To: Linux-MM , linux-kernel CC: Andrew Morton , Matthew Wilcox , Yu Zhao , Shakeel Butt , Alex Shi , Huang Ying Message-ID: <364d7ce9-ccb7-fa04-7067-44a96be87060@huawei.com> Date: Mon, 29 Mar 2021 21:18:20 +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 Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.179.86] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, I am investigating the swap code, and I found the below possible race window: CPU 1 CPU 2 ----- ----- do_swap_page skip swapcache case (synchronous swap_readpage) alloc_page_vma swapoff release swap_file, bdev, or ... swap_readpage check sis->flags is ok access swap_file, bdev or ...[oops!] si->flags = 0 The swapcache case is ok because swapoff will wait on the page_lock of swapcache page. Is this will really happen or Am I miss something ? Any reply would be really grateful. Thanks! :)