From: rtm@csail.mit.edu
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS client RPC bug
Date: Thu, 04 Nov 2021 16:36:19 -0400 [thread overview]
Message-ID: <7772.1636058179@crash.local> (raw)
In-Reply-To: Your message of "Thu, 04 Nov 2021 20:29:07 -0000." <bda6f973c4d77483f35440bfa5caa9ae82f4df17.camel@hammerspace.com>
> I'm a little surprised that xdr_inline_decode() didn't barf, though.
> Isn't size_t a 64-bit type on riscv64?
I believe hdr->taglen is a u32.
prev parent reply other threads:[~2021-11-04 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 20:10 NFS client RPC bug rtm
2021-11-04 20:29 ` Trond Myklebust
2021-11-04 20:36 ` rtm [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=7772.1636058179@crash.local \
--to=rtm@csail.mit.edu \
--cc=anna.schumaker@netapp.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