All of lore.kernel.org
 help / color / mirror / Atom feed
From: dan carpenter <error27@email.com>
To: Mike Fedyk <mfedyk@matchmail.com>, LKML <linux-kernel@vger.kernel.org>
Cc: neilb@cse.unsw.edu.au, nfs@lists.sourceforge.net
Subject: Re: bad: scheduling while atomic in nfs with 2.6.3
Date: Tue, 2 Mar 2004 20:15:43 -0800	[thread overview]
Message-ID: <200403022015.43151.error27@email.com> (raw)
In-Reply-To: <40454C6F.5020901@matchmail.com>

On Tuesday 02 March 2004 07:09 pm, Mike Fedyk wrote:
> I'm running 2.6.3-zonebal-lofft-slabfaz
> Call Trace:
>   [<c012258d>] __might_sleep+0x9d/0xe0
>   [<c01651d8>] deactivate_super+0x58/0x100
>   [<f89e9fba>] svc_export_put+0x7a/0x80 [nfsd]

The bad call path goes something like this:
svc_export_put() -> mntput() ->  __mntput() -> deactivate_super()
-> down_write() -> might_sleep()

I don't have a fix.  Neil Brown might.  I've CC'd him.

regards,
dan carpenter

  reply	other threads:[~2004-03-03  4:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  3:09 bad: scheduling while atomic in nfs with 2.6.3 Mike Fedyk
2004-03-03  4:15 ` dan carpenter [this message]
2004-03-03  5:30 ` J. Bruce 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=200403022015.43151.error27@email.com \
    --to=error27@email.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    /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.