From: "J. Bruce Fields" <bfields@fieldses.org>
To: Anna Schumaker <schumakeranna@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Jorge Mora <jmora1300@gmail.com>
Subject: Re: xfstests generic/263
Date: Tue, 27 Oct 2020 16:14:18 -0400 [thread overview]
Message-ID: <20201027201418.GA4564@fieldses.org> (raw)
In-Reply-To: <20201027200507.GD1644@fieldses.org>
On Tue, Oct 27, 2020 at 04:05:07PM -0400, J. Bruce Fields wrote:
> On Tue, Oct 27, 2020 at 03:59:56PM -0400, Anna Schumaker wrote:
> > On Tue, Oct 27, 2020 at 1:49 PM J. Bruce Fields <bfields@fieldses.org> wrote:
> > >
> > > Generic/263 is failing whenever client and server both supports
> > > READ_PLUS.
> > >
> > > I'm not even sure the failure is wrong. The NFS FALLOC operation doesn't
> > > support those other other fallocate modes, are they implemented elsewhere in
> > > the kernel or libc somehow? Anyway, odd that it would have anything to do with
> > > READ_PLUS.
> >
> > I just ran xfstests, and I'm seeing this too. The test passes using
> > basic READ on v4.2, so there might be something farther down the log
> > that diff is cutting off. I'll see if anything sticks out to me this
> > week.
>
> Thanks!
>
> Also, wireshark doesn't seem to be parsing READ_PLUS replies correctly.
> Cc'ing Jorge since he seems to have been the last to touch that code.
Oops, ignore me!
I was actually just running the wrong version of wireshark, with a
version built with Jorge's patch it's fine.
--b.
next prev parent reply other threads:[~2020-10-27 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 17:49 xfstests generic/263 J. Bruce Fields
2020-10-27 19:59 ` Anna Schumaker
2020-10-27 20:05 ` J. Bruce Fields
2020-10-27 20:14 ` J. Bruce Fields [this message]
2020-11-05 20:52 ` J. Bruce Fields
2020-11-05 21:10 ` Anna Schumaker
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=20201027201418.GA4564@fieldses.org \
--to=bfields@fieldses.org \
--cc=jmora1300@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=schumakeranna@gmail.com \
/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.