From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7D37921ADCB; Sat, 1 Nov 2025 05:01:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761973274; cv=none; b=LhAx4OyC2ZpaskM9Q8CNKc90Dmsyhy5WOmoN85LvT5W696QHr6fYq+6kOry0Q+e8Z+SrFyXgu9/oh/WqXKU5SrcKJd39C+HxQEo6kRnLd5gTqpzsu/GtNn+g2EHlDBe0Aa3yoR0uZZjJO2J238qsPr+K0HGajw7AmFlTkw0yFyY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761973274; c=relaxed/simple; bh=MSmFonQhLiVrYFtlSYTNKc2d0hY0+PZpclkFF5lut+U=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=XmxCwhm8sqBPyD7ezKDbSx/izBjH1BmfIu7NtBx+n2J24V9H/dqAxKp1bBNGWejIstvffGOU+jdFLz2gwYYK9YT3J2y2dkns8vyHw/CCtN5LQatzgiS2AxwnQlwPNnHDju823UkeV6EmVxMnEFoMblYJ+D0tl/h7+8d7JIlMLU8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=m8cBoJTe; arc=none smtp.client-ip=90.155.50.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="m8cBoJTe" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=nUfYsQtKHPf6wGb5urLnNs0QXXFwsJ1uqZTAIsOnWO8=; b=m8cBoJTe+4lqxnFOY3CicYWrN9 vVSfzrov1mXQcm/ejH+7snvW0fku6j+TSEDgJwiDbvk/BnnBQSZsiKKBCmg37krQiQeR+s0VwfA5K Hgb2urZ/RwlHXrFPYj+wGmHk0aTco+RQek0qer0J512Q9VkTZxrn56/xiC92KtH6U1NMvNNuLGc/8 oUfXrHCVC2jjaTuwC47G3NDf7Tly13LH93JapnK3sbtB6XFfe0Gp0GQvvXHN+08/6IPxhXBB7b7+H FTjNGlQdcG5NuSfTy3cYcsYhNyZRXe+Ir078vlZrvPRsl1FGaknm4HGKCrGkIO0KaxG8AyLzTpgGE UQVLjJpA==; Received: from willy by casper.infradead.org with local (Exim 4.98.2 #2 (Red Hat Linux)) id 1vF3jL-00000001FAo-1qO9; Sat, 01 Nov 2025 05:00:47 +0000 Date: Sat, 1 Nov 2025 05:00:47 +0000 From: Matthew Wilcox To: Hugh Dickins Cc: Kiryl Shutsemau , Andrew Morton , David Hildenbrand , Alexander Viro , Christian Brauner , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Rik van Riel , Harry Yoo , Johannes Weiner , Shakeel Butt , Baolin Wang , "Darrick J. Wong" , Dave Chinner , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCHv3 1/2] mm/memory: Do not populate page table entries beyond i_size Message-ID: References: <20251027115636.82382-1-kirill@shutemov.name> <20251027115636.82382-2-kirill@shutemov.name> <20251027153323.5eb2d97a791112f730e74a21@linux-foundation.org> <9e2750bf-7945-cc71-b9b3-632f03d89a55@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e2750bf-7945-cc71-b9b3-632f03d89a55@google.com> On Wed, Oct 29, 2025 at 02:45:52AM -0700, Hugh Dickins wrote: > But you're giving yourself too hard a time of backporting with your > 5.10 Fixee 01c70267053d for 1/2: the only filesystem which set the > flag then was tmpfs, which you're now excepting. The flag got > renamed later (in 5.16) and then in 5.17 at last there was another > filesystem to set it. So, this 1/2 would be > > Fixes: 6795801366da ("xfs: Support large folios") I haven't been able to keep up with this patchset -- sorry. But this problem didn't exist until bs>PS support was added because we would never add a folio to the page cache which extended beyond i_size before. We'd shrink the folio order allocated in do_page_cache_ra() (actually, we still do, but page_cache_ra_unbounded() rounds it up again). So it doesn't fix that commit at all, but something far more recent.