All of lore.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Rue Mohr <sn0297@sunshine.net>, linux-nfs@vger.kernel.org
Subject: Re: nfs kernel server bug
Date: Tue, 23 Feb 2021 17:59:18 -0500	[thread overview]
Message-ID: <20210223225918.GE8042@fieldses.org> (raw)
In-Reply-To: <5B1E0F4D-F26F-4CB5-858A-E49D0819C864@redhat.com>

On Mon, Feb 08, 2021 at 06:58:38AM -0500, Benjamin Coddington wrote:
> On 7 Feb 2021, at 12:18, Rue Mohr wrote:
> 
> >I'm having an issue where the kernel server is dishing out all
> >zeros for file content being read over NFS. The file byte count is
> >correct.
> >Writing files is fine.
> >With the same client, a different server works just fine.
> >
> >I have been trying to pin this down, so far all I know is that the
> >packets from the server actually contain zeros for the file
> >contents.
> >
> >The troubled server kernel is 5.4.1
> >
> >Has anyone encountered this or is it just me?
> 
> Haven't heard of this before, but sounds like a fascinating problem.
> 
> What version of nfs, and what security?  You're seeing READ
> operations returning
> with rsize-ed blocks of all-zero data in a network capture?

It might also be useful to know what filesystem you're exporting, with
what mount and export options.

--b.

      reply	other threads:[~2021-02-23 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 17:18 nfs kernel server bug Rue Mohr
2021-02-08 11:58 ` Benjamin Coddington
2021-02-23 22:59   ` J. Bruce Fields [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=20210223225918.GE8042@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bcodding@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sn0297@sunshine.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 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.