All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew W Elble <aweits@rit.edu>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: Bruce James Fields <bfields@fieldses.org>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: upgrade/downgrade race
Date: Sat, 12 Sep 2015 08:27:14 -0400	[thread overview]
Message-ID: <m27fnvx1p9.fsf@discipline.rit.edu> (raw)
In-Reply-To: <20150912081037.6658649c@tlielax.poochiereds.net> (Jeff Layton's message of "Sat, 12 Sep 2015 08:10:37 -0400")

> Andrew, could you test this patch out? This just covers open and lock
> stateids. If it works, I'll clean up the comments and resend it to the
> list as a PATCH email.

Will do, thank you!

> Assuming that it does, we'll need to consider what (if anything) to do
> about layout stateids...

-- 
Andrew W. Elble
aweits@discipline.rit.edu
Infrastructure Engineer, Communications Technical Lead
Rochester Institute of Technology
PGP: BFAD 8461 4CCF DC95 DA2C B0EB 965B 082E 863E C912

  reply	other threads:[~2015-09-12 12:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 13:37 upgrade/downgrade race Andrew W Elble
2015-09-09 15:58 ` Andrew W Elble
2015-09-09 17:12 ` Trond Myklebust
2015-09-09 17:49   ` Trond Myklebust
2015-09-09 18:49     ` Jeff Layton
2015-09-09 19:01       ` Trond Myklebust
2015-09-09 19:18         ` Jeff Layton
2015-09-09 20:40           ` Bruce James Fields
2015-09-09 21:00             ` Jeff Layton
2015-09-09 21:39               ` Bruce James Fields
2015-09-09 22:08                 ` Jeff Layton
2015-09-12 12:10                 ` Jeff Layton
2015-09-12 12:27                   ` Andrew W Elble [this message]
2015-09-15 11:49                   ` Andrew W Elble
2015-09-15 11:59                     ` Jeff Layton
2015-09-09 19:04       ` Bruce James Fields

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=m27fnvx1p9.fsf@discipline.rit.edu \
    --to=aweits@rit.edu \
    --cc=bfields@fieldses.org \
    --cc=jeff.layton@primarydata.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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.