From: Matthew Wilcox <willy@infradead.org>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
linux-fsdevel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
linux-xfs@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Miklos Szeredi <miklos@szeredi.hu>, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <liam.howlett@oracle.com>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: next-20250721 arm64 16K and 64K page size WARNING fs fuse file.c at fuse_iomap_writeback_range
Date: Mon, 28 Jul 2025 18:34:26 +0100 [thread overview]
Message-ID: <aIe0ouF9tsuIO58_@casper.infradead.org> (raw)
In-Reply-To: <CAJnrk1ZYR=hM5k90H57tOv=fe6F-r8dO+f3wNuCT_w3j8YNYNQ@mail.gmail.com>
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?
next prev parent reply other threads:[~2025-07-28 17:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 11:44 next-20250721 arm64 16K and 64K page size WARNING fs fuse file.c at fuse_iomap_writeback_range Naresh Kamboju
2025-07-23 14:46 ` Darrick J. Wong
2025-07-23 18:42 ` Joanne Koong
2025-07-23 21:20 ` Darrick J. Wong
2025-07-23 22:37 ` Joanne Koong
2025-07-24 19:14 ` Joanne Koong
2025-07-26 1:16 ` Joanne Koong
2025-07-28 17:14 ` Darrick J. Wong
2025-07-28 17:44 ` Joanne Koong
2025-07-28 19:11 ` Darrick J. Wong
2025-07-28 21:28 ` Joanne Koong
2025-07-29 20:21 ` Darrick J. Wong
2025-07-29 23:23 ` Joanne Koong
2025-07-29 23:40 ` Darrick J. Wong
2025-07-30 22:54 ` Joanne Koong
2025-07-31 17:55 ` Darrick J. Wong
2025-07-31 20:48 ` Joanne Koong
2025-08-12 16:42 ` Darrick J. Wong
2025-07-28 17:34 ` Matthew Wilcox [this message]
2025-07-28 17:55 ` Joanne Koong
2025-07-28 18:43 ` Darrick J. Wong
2025-07-23 23:15 ` Joanne Koong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aIe0ouF9tsuIO58_@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=joannelkoong@gmail.com \
--cc=liam.howlett@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=miklos@szeredi.hu \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).