From: Dominique Martinet <asmadeus@codewreck.org>
To: Barret Rhoden <brho@google.com>
Cc: David Howells <dhowells@redhat.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,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] 9p: treat read return values of 0 as EOF
Date: Thu, 29 Oct 2026 15:04:35 +0900 [thread overview]
Message-ID: <auLh89BhlBRC2G6E@codewreck.org> (raw)
In-Reply-To: <3d5f70fa-64e6-4df5-bda9-6d3cdd00682b@google.com>
Barret Rhoden wrote on Fri, Oct 23, 2026 at 08:19:33AM -0400:
> On 9/13/26 11:49 AM, Dominique Martinet wrote:
> > Sorry for dropping the ball here, I haven't had any time to do 9p stuff
> > at all recently and the wave of LLM generated patches hasn't helped...
>
> no problem.
>
> as far as resolving the underlying netfs stuff goes, i don't know how much
> of the logic about "are we at EOF" should be in netfs or in the servers
> (9p).
Right, I don't either which is why I was hoping for David to follow up
:-D
> would you be OK with merging my original patch so that at least 9p works?
Well, it's certainly better than returning ENODATA to userspace, so
let's go forward with that.
It still leaves much to be desired (cache enabled, symlinks...), but
that can come later if someone has energy to fight this windmill
Thank you for your time,
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2026-10-29 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <akfHGcqke9qixd3Q@codewreck.org>
[not found] ` <20260702090941.1298188-1-brho@google.com>
[not found] ` <2237820.1783934942@warthog.procyon.org.uk>
[not found] ` <f7005841-80a9-4c21-a114-6cfd6ee63a58@google.com>
2026-09-13 15:49 ` [PATCH] 9p: treat read return values of 0 as EOF Dominique Martinet
2026-10-23 12:19 ` Barret Rhoden
2026-10-29 6:04 ` Dominique Martinet [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=auLh89BhlBRC2G6E@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=brho@google.com \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox