On Mon, Jun 16, 2025 at 9:38 PM Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > > On Mon, Jun 16, 2025 at 12:18:21PM -0700, Joanne Koong wrote: > > Nothing in this series uses the iomap read path, but fuse might be > > used in environments where CONFIG_BLOCK isn't set. What I'm trying to > > do with this patch is move the logic in iomap readpage that's block / > > bio dependent out of buffered-io.c and gate that behind a #ifdef > > CONFIG_BLOCK check so that fuse can use buffered-io.c without breaking > > compilation for non-CONFIG_BLOCK environments > > Ah, ok. Are you fine with getting something that works for fuse first, > and then we look into !CONFIG_BLOCK environments as a next step? I think the fuse iomap work has a hard dependency on the CONFIG_BLOCK work else it would break backwards compatibility for fuse (eg non-CONFIG_BLOCK environments wouldn't be able to compile/use fuse anymore)
