From: Jens Axboe <jens.axboe@oracle.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Simple script that locks up my box with recent kernels
Date: Wed, 22 Nov 2006 11:57:03 +0100 [thread overview]
Message-ID: <20061122105703.GZ8055@kernel.dk> (raw)
In-Reply-To: <9a8748490611220255v53bc667y74b05e2b69281f25@mail.gmail.com>
On Wed, Nov 22 2006, Jesper Juhl wrote:
> On 22/11/06, Jens Axboe <jens.axboe@oracle.com> wrote:
> >On Tue, Nov 21 2006, Linus Torvalds wrote:
> >> I don't think we use any irq-disable locking in the VM itself, but I
> >could
> >> imagine some nasty situation with the block device layer getting into a
> >> deadlock with interrupts disabled when it runs out of queue entries and
> >> cannot allocate more memory..
> >
> >Not likely. Request allocation is done with GFP_NOIO and backed by a
> >memory pool, so as long the vm doesn't go totally nuts because
> >__GFP_WAIT is set, we should be safe there. If it did go crazy, I
> >suspect a sysrq-t would still work.
> >
> >If bouncing is involved for swap, we do have a potential deadlock issue
> >that isn't fixed yet. I just whipped up this completely untested patch,
> >it should shed some light on that issue.
> >
> Thanks Jens, I'll apply that later tonight and force a few lockups and
> see if I get any extra details with that patch.
Can you post a full dmesg too, as well as clarify which device holds the
swap space?
--
Jens Axboe
next prev parent reply other threads:[~2006-11-22 10:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 23:36 Simple script that locks up my box with recent kernels Jesper Juhl
2006-10-06 23:54 ` Andrew Morton
2006-10-07 0:06 ` Jesper Juhl
2006-10-07 0:21 ` Jesper Juhl
2006-10-07 3:11 ` Linus Torvalds
2006-10-07 21:02 ` Jesper Juhl
2006-10-07 21:25 ` Linus Torvalds
2006-10-08 23:33 ` Jesper Juhl
2006-10-16 22:45 ` Jesper Juhl
2006-10-16 23:04 ` Linus Torvalds
2006-10-16 23:13 ` Jesper Juhl
2006-10-23 20:30 ` Jesper Juhl
2006-11-22 0:46 ` Jesper Juhl
2006-11-22 2:36 ` Linus Torvalds
2006-11-22 3:25 ` Dave Jones
2006-11-22 3:44 ` Linus Torvalds
2006-11-22 3:49 ` Dave Jones
2006-11-22 10:32 ` Pádraig Brady
2006-11-22 17:58 ` Dave Jones
2006-11-22 8:03 ` Jens Axboe
2006-11-22 10:55 ` Jesper Juhl
2006-11-22 10:57 ` Jens Axboe [this message]
2006-11-22 11:04 ` Jesper Juhl
2006-11-22 11:07 ` Jens Axboe
2006-11-23 23:52 ` Jesper Juhl
2006-11-24 6:52 ` Jens Axboe
2006-11-24 9:41 ` Jesper Juhl
2006-11-24 9:46 ` Jens Axboe
2006-11-24 9:52 ` Jesper Juhl
2006-11-23 10:22 ` Jesper Juhl
2006-11-23 23:48 ` Jesper Juhl
2006-11-22 11:00 ` Jesper Juhl
2006-11-24 0:50 ` Jesper Juhl
2006-10-07 3:40 ` Grant Coady
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=20061122105703.GZ8055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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.