On Fri, Jul 11, 2025 at 09:46:11PM -0700, Darrick J. Wong wrote:
[fullquote deleted. Any chance you could only quote the actually relevant
parts as per usual email ettiquette?]
> > @@ -1419,6 +1449,15 @@ static ssize_t fuse_cache_write_iter(struct kiocb *iocb, struct iov_iter *from)
> > goto out;
> > written = direct_write_fallback(iocb, from, written,
> > fuse_perform_write(iocb, from));
>
> Random unrelatd question: does anyone know why fuse handles IOCB_DIRECT
> in its fuse_cache_{read,write}_iter functions and /also/ sets
> ->direct_IO? I thought filesystems only did one or the other, not both.
Nothing really should be setting ->direct_IO these days except for
legacy reasons. It's another one of those method that aren't methods
but just callbacks that require file system specific context.
