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 E35071E5B60; Mon, 28 Jul 2025 17:34:29 +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=1753724072; cv=none; b=CE5B9d4146dc8Jh7nBKIs+uAOuuwxFgOhHlz92gGg1KeEDS7V1bbj1v2jQiMDVgs+L8qWJUiWxj/KdBybhtI+Epr7mvl6+0vLqVkUJDvmdkNPwpZEE4EN6frZ6DEhAI9g4aHyzJKouMCt+M3/VMIIicMTCf+hZme1QM+iRCv7ec= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1753724072; c=relaxed/simple; bh=H+qJ3VsmLYnhXL8M1dlj3FhFxU65ltQR/R9/oXPPEPQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=sU9BA+DA8fUg9oxIrazKFXRWFjI9Zx8dRcXjOELCywnc6zxIhqjCkFbg/OAwld9bdhgLLjMtMYBZsqor02LHHdXagTB+gJxP8pSQVWAJzrCPeOkBGzYFx7d2zyTn/aQYCelUb1x9w4f/OyGiqifRisOb6yTVEoCfrpeXcYZX71k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (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=lfmn6Cqk; arc=none smtp.client-ip=90.155.50.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (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="lfmn6Cqk" 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=UqDXWAxgebVs6SjAbN0f5M+jCa7IiTLdF4RA9QqoSVg=; b=lfmn6CqkKhTXqOeyMQ1VarfYAP +btVaS1jPbtSnxWAdty5IIUiuM66govjO0Sho7Y5dOueCDjX+SJWeoUMPxnpt/2wNOBG5dB0ul1vZ k0spiHeceACX7KDWckEZiOpcS0Pkl0nNeQkYeiJ5uIIoc1YIY5j+RRMUll5+eO030vwbcfYsYlxS6 UEyq5xgKSq+kG84qqFMi0Mi7+E44j42/OrE2WKnwF8iMnVH/yC+89p/iq40irvIkSHu3EZ92qipMX JU28Ggr9sfmYB0E1d5IHq1YV+65QDsyLmTOJH0as7gLtBGgQh9ES37Dc5aVTW+S4EQ27GhNFPBrzl XbO8XQNg==; Received: from willy by casper.infradead.org with local (Exim 4.98.2 #2 (Red Hat Linux)) id 1ugRk2-0000000FyPy-11wc; Mon, 28 Jul 2025 17:34:26 +0000 Date: Mon, 28 Jul 2025 18:34:26 +0100 From: Matthew Wilcox To: Joanne Koong Cc: "Darrick J. Wong" , Naresh Kamboju , linux-fsdevel@vger.kernel.org, linux-mm , linux-xfs@vger.kernel.org, open list , lkft-triage@lists.linaro.org, Linux Regressions , Miklos Szeredi , Jan Kara , Andrew Morton , Christian Brauner , Lorenzo Stoakes , "Liam R. Howlett" , Arnd Bergmann , Dan Carpenter , Anders Roxell , Ben Copeland Subject: Re: next-20250721 arm64 16K and 64K page size WARNING fs fuse file.c at fuse_iomap_writeback_range Message-ID: References: <20250723144637.GW2672070@frogsfrogsfrogs> <20250723212020.GY2672070@frogsfrogsfrogs> Precedence: bulk X-Mailing-List: linux-xfs@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: On Fri, Jul 25, 2025 at 06:16:15PM -0700, Joanne Koong wrote: > > > > > Also, I just noticed that apparently the blocksize can change > > > > > dynamically for an inode in fuse through getattr replies from the > > > > > server (see fuse_change_attributes_common()). This is a problem since > > > > > the iomap uses inode->i_blkbits for reading/writing to the bitmap. I > > > > > think we will have to cache the inode blkbits in the iomap_folio_state > > > > > struct unfortunately :( I'll think about this some more and send out a > > > > > patch for this. Does this actually happen in practice, once you've started _using_ the block device? Rather than all this complicated stuff to invalidate the page cache based on the fuse server telling us something, maybe just declare the server to be misbehaving and shut the whole filesystem down?