All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@primarydata.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org, trond.myklebust@primarydata.com,
	hch@infradead.org
Subject: [PATCH v2 0/2] nfsd: preliminary patches for client_mutex removal
Date: Fri,  6 Jun 2014 09:07:04 -0400	[thread overview]
Message-ID: <1402060026-26511-1-git-send-email-jlayton@primarydata.com> (raw)

This is a respin of the last two patches in the 9 patch series I posted
last week. Bruce dropped patch #8, as it caused a lockdep pop due to
lock inversion between the i_lock and the state_lock. Patch #9 was
dropped due to objections from Christoph. Bruce indicated that he would
take the others, so I won't repost them here.

These two patches should address the previous concerns -- let me know if
there are any objections.

Jeff Layton (1):
  nfsd: avoid taking the state_lock while holding the i_lock

Trond Myklebust (1):
  nfsd: Protect addition to the file_hashtbl

 fs/nfsd/nfs4callback.c |   9 +++-
 fs/nfsd/nfs4state.c    | 123 ++++++++++++++++++++++++++++++++++++-------------
 fs/nfsd/state.h        |   2 +
 3 files changed, 101 insertions(+), 33 deletions(-)

-- 
1.9.3


             reply	other threads:[~2014-06-06 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 13:07 Jeff Layton [this message]
2014-06-06 13:07 ` [PATCH v2 1/2] nfsd: Protect addition to the file_hashtbl Jeff Layton
2014-06-06 14:14   ` Christoph Hellwig
2014-06-06 13:07 ` [PATCH v2 2/2] nfsd: avoid taking the state_lock while holding the i_lock Jeff Layton
2014-06-07 14:09   ` Christoph Hellwig
2014-06-07 14:28     ` Jeff Layton
2014-06-07 14:31       ` Christoph Hellwig
2014-06-07 14:34         ` Jeff Layton

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=1402060026-26511-1-git-send-email-jlayton@primarydata.com \
    --to=jlayton@primarydata.com \
    --cc=bfields@fieldses.org \
    --cc=hch@infradead.org \
    --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.