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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 94D9BC433F5 for ; Mon, 27 Sep 2021 22:25:03 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 1CCA0610A2 for ; Mon, 27 Sep 2021 22:25:02 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 1CCA0610A2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 160AB900002; Mon, 27 Sep 2021 18:25:02 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 110D76B0072; Mon, 27 Sep 2021 18:25:02 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id ECC6A900002; Mon, 27 Sep 2021 18:25:01 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0113.hostedemail.com [216.40.44.113]) by kanga.kvack.org (Postfix) with ESMTP id D942A6B0071 for ; Mon, 27 Sep 2021 18:25:01 -0400 (EDT) Received: from smtpin14.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 8F35D181F6CA6 for ; Mon, 27 Sep 2021 22:25:01 +0000 (UTC) X-FDA: 78634784802.14.08C6FF4 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf21.hostedemail.com (Postfix) with ESMTP id EDF01D036400 for ; Mon, 27 Sep 2021 22:25:00 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id E9A7C61157 for ; Mon, 27 Sep 2021 22:24:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1632781499; bh=TyKEhPGij+CGTbxdLG5vYotUYB4WHx9ib8bzmK1W8v4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Bf+EOvNdmkZ32sSz5ALoF7qIusFlbGALBf8935PjknFf/SHPszFTX0YkCyxt38X1A pbG+dpt+FGsS0Y7aMTSz5hC/PuIYikOSOUj7UKtvcAVnji+UiC5BHC9gqFg5SHUF4s SECd94rStr7A1XuWeVlrjpiL+D+kEAGPM7iJdcyDXigExE8Z56bo6KcTM/UXYLQB5L QgFTQOF49SyKxSXl8mVSX1fYyM3ilqigdGosIRixRjnKgiG8luh7gnVQAwGudFi4rE 6cnQJjmlDSHiO2TKleEB5WphAeR1M6MsVGR3HTX6WDhNpaYPBhn6XDywCmh2434oHb e6oL7b15x1Ufg== Received: by mail-lf1-f52.google.com with SMTP id i25so84427574lfg.6 for ; Mon, 27 Sep 2021 15:24:59 -0700 (PDT) X-Gm-Message-State: AOAM5331jktnx3xFexdphToGZ6MTsHnns06H0CoBwwSO8rlf7pwew9Tv 8k7Df6pNfupzqjeeOUaetKNFCMRCWCCby8wCPYM= X-Google-Smtp-Source: ABdhPJwf8HSgziRuGH35BctWGCYrnpxVuInOklCOyvOvq7OH5Mc9BdMMewJuG7g+raQXkmf6rSriyCTPQ6TQNStLFXY= X-Received: by 2002:a05:6512:39c4:: with SMTP id k4mr2231945lfu.14.1632781498176; Mon, 27 Sep 2021 15:24:58 -0700 (PDT) MIME-Version: 1.0 References: <20210906121200.57905-1-rongwei.wang@linux.alibaba.com> <20210922070645.47345-2-rongwei.wang@linux.alibaba.com> <20210923194343.ca0f29e1c4d361170343a6f2@linux-foundation.org> <9e41661d-9919-d556-8c49-610dae157553@linux.alibaba.com> In-Reply-To: <9e41661d-9919-d556-8c49-610dae157553@linux.alibaba.com> From: Song Liu Date: Mon, 27 Sep 2021 15:24:47 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 1/2] mm, thp: check page mapping when truncating page cache To: Rongwei Wang Cc: Andrew Morton , Matthew Wilcox , Linux MM , Linux Kernel Mailing List , William Kucharski , Hugh Dickins Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Authentication-Results: imf21.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=Bf+EOvNd; spf=pass (imf21.hostedemail.com: domain of song@kernel.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=song@kernel.org; dmarc=pass (policy=none) header.from=kernel.org X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: EDF01D036400 X-Stat-Signature: em9ajrp613mmr1d7fdb46kka7gcunkc5 X-HE-Tag: 1632781500-42821 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, Sep 24, 2021 at 12:12 AM Rongwei Wang wrote: > > > > On 9/24/21 10:43 AM, Andrew Morton wrote: > > On Thu, 23 Sep 2021 01:04:54 +0800 Rongwei Wang wrote: > > > >> > >> > >>> On Sep 22, 2021, at 7:37 PM, Matthew Wilcox wro= te: > >>> > >>> On Wed, Sep 22, 2021 at 03:06:44PM +0800, Rongwei Wang wrote: > >>>> Transparent huge page has supported read-only non-shmem files. The f= ile- > >>>> backed THP is collapsed by khugepaged and truncated when written (fo= r > >>>> shared libraries). > >>>> > >>>> However, there is race in two possible places. > >>>> > >>>> 1) multiple writers truncate the same page cache concurrently; > >>>> 2) collapse_file rolls back when writer truncates the page cache; > >>> > >>> As I've said before, the bug here is that somehow there is a writable= fd > >>> to a file with THPs. That's what we need to track down and fix. > >> Hi, Matthew > >> I am not sure get your means. We know =E2=80=9Cmm, thp: relax the VM_D= ENYWRITE constraint on file-backed THPs" > >> Introduced file-backed THPs for DSO. It is possible {very rarely} for = DSO to be opened in writeable way. > >> > >> ... > >> > >>> https://lore.kernel.org/linux-mm/YUdL3lFLFHzC80Wt@casper.infradead.or= g/ > >> All in all, what you mean is that we should solve this race at the sou= rce? > > > > Matthew is being pretty clear here: we shouldn't be permitting > > userspace to get a writeable fd for a thp-backed file. > > > > Why are we permitting the DSO to be opened writeably? If there's a > > legitimate case for doing this then presumably "mm, thp: relax the > There is a use case to stress file-backed THP within attachment. > I test this case in a system which has enabled CONFIG_READ_ONLY_THP_FOR_F= S: > > $ gcc -Wall -g -o stress_madvise_dso stress_madvise_dso.c > $ ulimit -s unlimited > $ ./stress_madvise_dso 10000 > > the meaning of above parameters: > 10000: the max test time; > : the DSO that will been mapped into file-backed THP by > madvise. It recommended that the text segment of DSO to be tested is > greater than 2M. > > The crash will been triggered at once in the latest kernel. And this > case also can used to trigger the bug that mentioned in our another patch= . Hmm.. I am not able to use the repro program to crash the system. Not sure what I did wrong. OTOH, does it make sense to block writes within khugepaged, like: diff --git i/mm/khugepaged.c w/mm/khugepaged.c index 045cc579f724e..ad7c41ec15027 100644 --- i/mm/khugepaged.c +++ w/mm/khugepaged.c @@ -51,6 +51,7 @@ enum scan_result { SCAN_CGROUP_CHARGE_FAIL, SCAN_TRUNCATED, SCAN_PAGE_HAS_PRIVATE, + SCAN_BUSY_WRITE, }; #define CREATE_TRACE_POINTS @@ -1652,6 +1653,11 @@ static void collapse_file(struct mm_struct *mm, /* Only allocate from the target node */ gfp =3D alloc_hugepage_khugepaged_gfpmask() | __GFP_THISNODE; + if (deny_write_access(file)) { + result =3D SCAN_BUSY_WRITE; + return; + } + new_page =3D khugepaged_alloc_page(hpage, gfp, node); if (!new_page) { result =3D SCAN_ALLOC_HUGE_PAGE_FAIL; @@ -1863,19 +1869,6 @@ static void collapse_file(struct mm_struct *mm, else { __mod_lruvec_page_state(new_page, NR_FILE_THPS, nr); filemap_nr_thps_inc(mapping); - /* - * Paired with smp_mb() in do_dentry_open() to ensure - * i_writecount is up to date and the update to nr_thps is - * visible. Ensures the page cache will be truncated if the - * file is opened writable. - */ - smp_mb(); - if (inode_is_open_for_write(mapping->host)) { - result =3D SCAN_FAIL; - __mod_lruvec_page_state(new_page, NR_FILE_THPS, -nr= ); - filemap_nr_thps_dec(mapping); - goto xa_locked; - } } if (nr_none) { @@ -1976,6 +1969,7 @@ static void collapse_file(struct mm_struct *mm, VM_BUG_ON(!list_empty(&pagelist)); if (!IS_ERR_OR_NULL(*hpage)) mem_cgroup_uncharge(*hpage); + allow_write_access(file); /* TODO: tracepoints */ }