From: Lee Revell <rlrevell@joe-job.com>
To: dwalker@mvista.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: 'BUG: scheduling with irqs disabled' when umounting NFS volume
Date: Fri, 08 Apr 2005 17:51:33 -0400 [thread overview]
Message-ID: <1112997093.12195.1.camel@mindpipe> (raw)
In-Reply-To: <1112992701.26296.16.camel@dhcp153.mvista.com>
On Fri, 2005-04-08 at 13:38 -0700, Daniel Walker wrote:
> I submitted a fix for this a while ago, I think ..
> interruptible_sleep_on()'s are broken ..
I saw the fix in -stable, but it does not seem to be in 2.6.12-rc2.
Lee
next prev parent reply other threads:[~2005-04-08 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 20:15 'BUG: scheduling with irqs disabled' when umounting NFS volume Lee Revell
2005-04-08 20:38 ` Daniel Walker
2005-04-08 21:51 ` Lee Revell [this message]
2005-04-11 16:29 ` Daniel Walker
2005-04-11 16:37 ` Lee Revell
2005-04-09 4:44 ` Ingo Molnar
2005-04-11 16:52 ` Daniel Walker
2005-04-10 10:27 ` Ingo Molnar
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=1112997093.12195.1.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=trond.myklebust@fys.uio.no \
/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