From: Trond Myklebust <trondmy@hammerspace.com>
To: "chuck.lever@oracle.com" <chuck.lever@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: error=Invalid slot
Date: Mon, 15 Apr 2019 16:24:41 +0000 [thread overview]
Message-ID: <eed8138c835abb5c9587f38aae6e3043df5b526d.camel@hammerspace.com> (raw)
In-Reply-To: <32DC3CC2-700B-4F44-849C-F229BAA2CB57@oracle.com>
On Mon, 2019-04-15 at 12:11 -0400, Chuck Lever wrote:
> >
> I was about to try something like this.
>
So, the reason for that approach is that I believe we can currently
leak ENOBUFS and possibly other errors in addition to EBADSLT through
the same race.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-04-15 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 15:04 error=Invalid slot Chuck Lever
2019-04-15 16:05 ` Trond Myklebust
2019-04-15 16:11 ` Chuck Lever
2019-04-15 16:24 ` Trond Myklebust [this message]
2019-04-17 19:50 ` Chuck Lever
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=eed8138c835abb5c9587f38aae6e3043df5b526d.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).