From: David Howells <dhowells@redhat.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: dhowells@redhat.com, Barret Rhoden <brho@google.com>,
Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 9p: treat read return values of 0 as EOF
Date: Mon, 13 Jul 2026 10:29:02 +0100 [thread overview]
Message-ID: <2237820.1783934942@warthog.procyon.org.uk> (raw)
In-Reply-To: <akfHGcqke9qixd3Q@codewreck.org>
This is kind of a weird situation. We're caching locally the content of files
aren't really regular files and probably shouldn't be cached. I'm not sure
what the best way to deal with that is. I wonder if there's some way to
detect that and mark then non-cacheable. (Assuming the server can be told not
to even serve them).
Can we detect that the EOF length doesn't match i_size and set a flag to say
"don't cache" in netfs_inode::flags?
David
prev parent reply other threads:[~2026-07-13 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:09 [PATCH] 9p: treat read return values of 0 as EOF Barret Rhoden
2026-07-03 14:28 ` Dominique Martinet
2026-07-05 21:22 ` Barret Rhoden
2026-07-13 9:29 ` David Howells [this message]
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=2237820.1783934942@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=brho@google.com \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=v9fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.