From: Nathan Scott <nathans@sgi.com>
To: Brad Fitzpatrick <brad@danga.com>
Cc: linux-kernel@vger.kernel.org, Lisa Phillips <lisa@danga.com>,
Mark Smith <marksmith@danga.com>,
linux-xfs@oss.sgi.com
Subject: Re: 2.6.9: unkillable processes during heavy IO
Date: Fri, 19 Nov 2004 15:59:37 +1100 [thread overview]
Message-ID: <20041119045937.GE1269@frodo> (raw)
In-Reply-To: <20041118050501.GD9834@frodo>
On Thu, Nov 18, 2004 at 04:05:01PM +1100, Nathan Scott wrote:
> I've reproduced it now with this tool and a simplified version
> of your recipe - I'll have a fix for you to try before too long.
Looks like a lock order problem - I have an experimental fix,
I'll send it to you shortly.
thanks.
--
Nathan
prev parent reply other threads:[~2004-11-19 6:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 22:15 2.6.9: unkillable processes during heavy IO Brad Fitzpatrick
2004-11-14 21:41 ` Alan Cox
2004-11-14 22:30 ` Andrew Morton
2004-11-14 22:45 ` Andries Brouwer
2004-11-15 7:39 ` Lenar Lõhmus
2004-11-16 13:56 ` Brad Fitzpatrick
2004-11-17 4:01 ` Andrew Morton
2004-11-17 4:55 ` Nathan Scott
2004-11-17 7:00 ` Brad Fitzpatrick
2004-11-18 5:05 ` Nathan Scott
2004-11-19 4:59 ` Nathan Scott [this message]
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=20041119045937.GE1269@frodo \
--to=nathans@sgi.com \
--cc=brad@danga.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lisa@danga.com \
--cc=marksmith@danga.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.