mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: dhowells@redhat.com, v9fs-developer@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, lucho@ionkov.net, ericvh@gmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] 9p: fix enodata when reading growing file
Date: Mon, 10 Jan 2022 11:18:42 +0000	[thread overview]
Message-ID: <3730531.1641813522@warthog.procyon.org.uk> (raw)
In-Reply-To: <20220110111444.926753-1-asmadeus@codewreck.org>

Dominique Martinet <asmadeus@codewreck.org> wrote:

> Reading from a file that was just extended by a write, but the write had
> not yet reached the server would return ENODATA as illustrated by this
> command:
> $ xfs_io -c 'open -ft test' -c 'w 4096 1000' -c 'r 0 1000'
> wrote 1000/1000 bytes at offset 4096
> 1000.000000 bytes, 1 ops; 0.0001 sec (5.610 MiB/sec and 5882.3529 ops/sec)
> pread: No data available
> 
> Fix this case by having netfs assume zeroes when reads from server come
> short like AFS and CEPH do
> 
> Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
> Co-authored-by: David Howells <dhowells@redhat.com>
> Cc: stable@vger.kernel.org

I think you want this also:

Fixes: eb497943fa21 ("9p: Convert to using the netfs helper lib to do reads and caching")

Reviewed-by: David Howells <dhowells@redhat.com>


  reply	other threads:[~2022-01-10 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 11:14 Dominique Martinet
2022-01-10 11:18 ` David Howells [this message]
2022-01-10 11:22 ` David Howells

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=3730531.1641813522@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=asmadeus@codewreck.org \
    --cc=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=stable@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®