From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Labiaga, Ricardo" <ricardo.labiaga@netapp.com>
Cc: bhalevy@panasas.com, pnfs@linux-nfs.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] nfsd41: renew_client() needs to be called with the client_mutex held
Date: Thu, 18 Jun 2009 13:48:47 -0400 [thread overview]
Message-ID: <20090618174847.GH9679@fieldses.org> (raw)
In-Reply-To: <C65FC9CE.8070%ricardo.labiaga@netapp.com>
On Thu, Jun 18, 2009 at 10:39:10AM -0700, Labiaga, Ricardo wrote:
> On 6/18/09 10:31 AM, "J. Bruce Fields" <bfields@fieldses.org> wrote:
>
> > On Wed, Jun 17, 2009 at 06:50:45PM -0700, Ricardo Labiaga wrote:
> >> renew_client() manipulates the client queue for lease renewal. Need to
> >> obtain the client_mutex before manipulating it.
> >>
> >> Signed-off-by: Ricardo Labiaga <Ricardo.Labiaga@netapp.com>
> >> ---
> >> fs/nfsd/nfs4state.c | 2 ++
> >> 1 files changed, 2 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> >> index 4cb5d1d..18258d7 100644
> >> --- a/fs/nfsd/nfs4state.c
> >> +++ b/fs/nfsd/nfs4state.c
> >> @@ -1537,7 +1537,9 @@ replay_cache:
> >> * Hold a session reference until done processing the compound:
> >> * nfsd4_put_session called only if the cstate slot is set.
> >> */
> >> + nfs4_lock_state();
> >> renew_client(session->se_client);
> >> + nfs4_unlock_state();
> >> nfsd4_get_session(session);
> >> out:
> >> spin_unlock(&sessionid_lock);
> >
> > We can't take a mutex while handling a spinlock. (And you should have
> > gotten warnings about this--not sure what kernel hacking config options
> > you may need turned on for that.)
> >
>
> Ah, OK. I didn't know that.
The deadlock:
Task 1 takes a spinlock.
Task 1 sleeps on the mutex.
Task 2 is scheduled in.
Task 2 requests the same spinlock, spins.
Now Task 2 is spinning waiting for the spinlock, keeping task 1 from
getting the cpu back and releaseing the spinlock. So, no sleeping under
spinlocks.
> > Possible hack: add a spinlock that for now will just cover the client
> > lru?
>
> Let me study this some more and see if I can simply drop the sessionid
> spinlock before renewing the state.
OK.
--b.
next prev parent reply other threads:[~2009-06-18 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 1:50 [PATCH 1/1] nfsd41: renew_client() needs to be called with the client_mutex held Ricardo Labiaga
2009-06-18 17:31 ` J. Bruce Fields
2009-06-18 17:39 ` Labiaga, Ricardo
2009-06-18 17:48 ` J. Bruce Fields [this message]
2009-06-18 17:51 ` Labiaga, Ricardo
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=20090618174847.GH9679@fieldses.org \
--to=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.org \
--cc=ricardo.labiaga@netapp.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.