From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Jiufei Xue <jiufei.xue@linux.alibaba.com>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
"aglo@umich.edu" <aglo@umich.edu>,
"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"joseph.qi@linux.alibaba.com" <joseph.qi@linux.alibaba.com>
Subject: Re: [bug report] task hang while testing xfstests generic/323
Date: Wed, 6 Mar 2019 11:09:34 -0500 [thread overview]
Message-ID: <20190306160934.GB3066@fieldses.org> (raw)
In-Reply-To: <46f5c870-f4fd-b29a-f5eb-eab39c4c1e89@linux.alibaba.com>
On Wed, Mar 06, 2019 at 05:59:39PM +0800, Jiufei Xue wrote:
> Hi Trond,
>
> >
> > No, that's quite weird... Were you able to catch this behaviour on
> > wireshark? It would be interesting to see if the server is actually
> > sending 2 SEQUENCE ops or if that is a corruption that occurs on the
> > client.
> >
>
> Many packages are dropped by kernel when I use tcpdump, so I am not sure
> whether the server is sending 2 SEQUENCE.
For what it's worth, tcpdump with -s200 or so should be enough to get
this. Or maybe capturing from a different machine could help?
> However, according to tracepoint nfsd_compound_status, the server is
> processing SEQUENCE op only once. I think it is more likely blames to
> the client.
If there was a bug in nfsd's xdr decoding, that'd happen after that
tracepoint. That'd be weird corruption, but perhaps all the
possibilites are weird at this point.
--b.
> Is there any other way to catch the behaviour?
>
> Thanks,
> Jiufei
>
next prev parent reply other threads:[~2019-03-06 16:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 10:10 [bug report] task hang while testing xfstests generic/323 Jiufei Xue
2019-02-28 22:26 ` Olga Kornievskaia
2019-02-28 23:56 ` Trond Myklebust
2019-03-01 5:19 ` Jiufei Xue
2019-03-01 5:08 ` Jiufei Xue
2019-03-01 8:49 ` Jiufei Xue
2019-03-01 13:08 ` Trond Myklebust
2019-03-02 16:34 ` Jiufei Xue
2019-03-04 15:20 ` Jiufei Xue
2019-03-04 15:50 ` Trond Myklebust
2019-03-05 5:09 ` Jiufei Xue
2019-03-05 14:45 ` Trond Myklebust
2019-03-06 9:59 ` Jiufei Xue
2019-03-06 16:09 ` bfields [this message]
2019-03-10 22:20 ` Olga Kornievskaia
2019-03-11 14:30 ` Trond Myklebust
2019-03-11 15:07 ` Olga Kornievskaia
2019-03-11 15:13 ` Olga Kornievskaia
2019-03-15 6:30 ` Jiufei Xue
2019-03-15 20:33 ` Olga Kornievskaia
2019-03-15 20:55 ` Trond Myklebust
2019-03-16 14:11 ` Jiufei Xue
2019-03-19 15:33 ` Olga Kornievskaia
2019-03-11 15:12 ` Trond Myklebust
2019-03-11 15:14 ` Olga Kornievskaia
2019-03-11 15:28 ` Trond Myklebust
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=20190306160934.GB3066@fieldses.org \
--to=bfields@fieldses.org \
--cc=Anna.Schumaker@netapp.com \
--cc=aglo@umich.edu \
--cc=jiufei.xue@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox