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 665F6C433F5 for ; Mon, 11 Oct 2021 19:58:06 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 0AD9160F5B for ; Mon, 11 Oct 2021 19:58:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 0AD9160F5B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 28929900002; Mon, 11 Oct 2021 15:58:05 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 2119B6B0072; Mon, 11 Oct 2021 15:58:05 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 08B12900002; Mon, 11 Oct 2021 15:58:05 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0122.hostedemail.com [216.40.44.122]) by kanga.kvack.org (Postfix) with ESMTP id E62EF6B0071 for ; Mon, 11 Oct 2021 15:58:04 -0400 (EDT) Received: from smtpin02.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 8568518259C31 for ; Mon, 11 Oct 2021 19:58:04 +0000 (UTC) X-FDA: 78685217688.02.E837ED1 Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com [209.85.208.46]) by imf20.hostedemail.com (Postfix) with ESMTP id 3E77CD001BA9 for ; Mon, 11 Oct 2021 19:58:04 +0000 (UTC) Received: by mail-ed1-f46.google.com with SMTP id r18so72160301edv.12 for ; Mon, 11 Oct 2021 12:58:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SKh3z8/eFx39DZqeLn4BLSOUQsWLVYgA6sDrH+x4Ulk=; b=mbTZFkNUWLVTd4DmzdjidHDoed1HvzabyqoqjfbSfDSfnZRHFe4aWbFxP2vttXkLYG fgY+vmdfVg8Mb4knc/uzjZjfn95JQUhUJc5HJhCh9fN/PBs8dpnFew/8uq99xByifowb zBoI1HjWz9lcOv+6aEy9mW2W1p2/VB7839rIxbIRaOXmHbm1i2/FZ2WkzUvWFgD76T78 vWYhEa2D/8Mzg57eBzfslfMifTlrCf/5JZr9d7Fgj+UFyhA3ujRICitMDtAQmdSFaVMD DAjQ7PSre+Q5+1Lizyafz9GbRf7aeSI9wN0kfkztsb23UEChT6x/uZTDYIyay0WtQ7DR fBzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SKh3z8/eFx39DZqeLn4BLSOUQsWLVYgA6sDrH+x4Ulk=; b=DcSirlI5s4VHNn2N/0Kwrui8jbvgZ+0qaWVzLzSUvq33uWFrAFLMnlQY3cyT1BBNNu NCDYGRPTzNTBmgwO/InSAcx1UkU85UjIYfc80OECx5GAmmfGfpUFFAoyD+8KaOtQO9W7 clqVNPijdaHiEAbcnj0l+3tBSK9HXcfxc8/5p5+oDAMK4WYekeI3KlpOey9+tep4hXyV qz9jBfZVV0YqjldRnKv2eJSYb+FbKtMnciEv6uuo7EsZnftVPNbNSl24kFDXhxztf4D0 Ggjx+6lIp5UDfHlL+hmfrKdLYbD4jByHXHoR5IXU7VduqI3LveUuMX5qVlcwwkLmgyw6 jZhQ== X-Gm-Message-State: AOAM530K9Yp9CQcN7E8/wcq7YoSTGbTuCxpQHvmU3qZdHts/7xM3/dae HcDsMAkERqRTLsnFtrIZWbNEhIWYE44g4U/INRo= X-Google-Smtp-Source: ABdhPJyvPma2sUPqNK2WXoa3c5nzFwAzXULxWPsz1UOgT2ZXXI0SzXbS+dZePUX9ENuRUxmAFHX8Z0px4jAlKssBXrA= X-Received: by 2002:a17:907:6297:: with SMTP id nd23mr28983343ejc.62.1633982282937; Mon, 11 Oct 2021 12:58:02 -0700 (PDT) MIME-Version: 1.0 References: <20210917205731.262693-1-shy828301@gmail.com> In-Reply-To: From: Yang Shi Date: Mon, 11 Oct 2021 12:57:51 -0700 Message-ID: Subject: Re: [PATCH] fs: buffer: check huge page size instead of single page for invalidatepage To: Matthew Wilcox Cc: Hugh Dickins , cfijalkovich@google.com, Song Liu , Andrew Morton , Hao Sun , Linux MM , Linux FS-devel Mailing List , Linux Kernel Mailing List , Song Liu Content-Type: text/plain; charset="UTF-8" X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 3E77CD001BA9 X-Stat-Signature: mgoujwwi8ogrgtmn1p8ifaoobgg47tdj Authentication-Results: imf20.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=mbTZFkNU; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (imf20.hostedemail.com: domain of shy828301@gmail.com designates 209.85.208.46 as permitted sender) smtp.mailfrom=shy828301@gmail.com X-HE-Tag: 1633982284-693891 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 Mon, Sep 20, 2021 at 3:35 PM Yang Shi wrote: > > On Mon, Sep 20, 2021 at 2:50 PM Matthew Wilcox wrote: > > > > On Mon, Sep 20, 2021 at 02:23:41PM -0700, Yang Shi wrote: > > > On Sun, Sep 19, 2021 at 7:41 AM Matthew Wilcox wrote: > > > > > > > > On Fri, Sep 17, 2021 at 05:07:03PM -0700, Yang Shi wrote: > > > > > > The debugging showed the page passed to invalidatepage is a huge page > > > > > > and the length is the size of huge page instead of single page due to > > > > > > read only FS THP support. But block_invalidatepage() would throw BUG if > > > > > > the size is greater than single page. > > > > > > > > Things have already gone wrong before we get to this point. See > > > > do_dentry_open(). You aren't supposed to be able to get a writable file > > > > descriptor on a file which has had huge pages added to the page cache > > > > without the filesystem's knowledge. That's the problem that needs to > > > > be fixed. > > > > > > I don't quite understand your point here. Do you mean do_dentry_open() > > > should fail for such cases instead of truncating the page cache? > > > > No, do_dentry_open() should have truncated the page cache when it was > > called and found that there were THPs in the cache. Then khugepaged > > should see that someone has the file open for write and decline to create > > new THPs. So it shouldn't be possible to get here with THPs in the cache. > I think Hugh's skipping special file patch (https://lore.kernel.org/linux-mm/a07564a3-b2fc-9ffe-3ace-3f276075ea5c@google.com/) could fix this specific BUG report and seems like a more proper fix to this. However, it still doesn't make too much sense to have thp_size passed to do_invalidatepage(), then have PAGE_SIZE hardcoded in a BUG assertion IMHO. So it seems this patch is still useful because block_invalidatepage() is called by a few filesystems as well, for example, ext4. Or I'm wondering whether we should call do_invalidatepage() for each subpage of THP in truncate_cleanup_page() since private is for each subpage IIUC. > AFAICT, it does so. > > In do_dentry_open(): > /* > * XXX: Huge page cache doesn't support writing yet. Drop all page > * cache for this file before processing writes. > */ > if (f->f_mode & FMODE_WRITE) { > /* > * Paired with smp_mb() in collapse_file() to ensure nr_thps > * is up to date and the update to i_writecount by > * get_write_access() is visible. Ensures subsequent insertion > * of THPs into the page cache will fail. > */ > smp_mb(); > if (filemap_nr_thps(inode->i_mapping)) > truncate_pagecache(inode, 0); > } > > > In khugepaged: > 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 = SCAN_FAIL; > __mod_lruvec_page_state(new_page, NR_FILE_THPS, -nr); > filemap_nr_thps_dec(mapping); > goto xa_locked; > } > > But I'm not quite sure if there is any race condition.