From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
suparna@in.ibm.com, pbadari@us.ibm.com, linux-aio@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: aio stress panic on 2.6.11-mm1
Date: Wed, 09 Mar 2005 11:59:20 +0000 [thread overview]
Message-ID: <3318.1110369560@redhat.com> (raw)
In-Reply-To: <20050309032832.159e58a4.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
> spin_lock_irq() is OK for down_*(), since down() can call schedule() anyway.
>
> spin_lock_irqsave() should be used in up_*() and I guess down_*_trylock(),
> although the latter shouldn't need to go into the slowpath anyway.
That's what I've done. I'm just testing my changes.
David
next prev parent reply other threads:[~2005-03-09 12:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050308170107.231a145c.akpm@osdl.org>
[not found] ` <1110327267.24286.139.camel@dyn318077bld.beaverton.ibm.com>
[not found] ` <18744.1110364438@redhat.com>
2005-03-09 11:04 ` aio stress panic on 2.6.11-mm1 Suparna Bhattacharya
2005-03-09 11:05 ` Andrew Morton
2005-03-09 11:07 ` Arjan van de Ven
2005-03-09 11:17 ` Andi Kleen
2005-03-09 11:28 ` Andrew Morton
2005-03-09 11:59 ` David Howells [this message]
2005-03-09 12:12 ` [PATCH] rwsem: Make rwsems use interrupt disabling spinlocks David Howells
2005-03-09 17:35 ` Badari Pulavarty
2005-03-09 19:18 ` Badari Pulavarty
2005-03-09 19:16 ` Badari Pulavarty
2005-03-09 19:42 ` Andrew Morton
2005-03-09 20:10 ` Arjan van de Ven
2005-03-11 9:40 ` Ingo Molnar
2005-03-11 10:07 ` Andrew Morton
2005-03-11 10:25 ` Ingo Molnar
2005-03-09 11:10 ` aio stress panic on 2.6.11-mm1 Arjan van de Ven
2005-03-09 11:21 ` Andi Kleen
2005-03-09 14:48 ` Suparna Bhattacharya
2005-03-09 21:58 ` David Howells
2005-03-09 11:11 ` Andi Kleen
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=3318.1110369560@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=suparna@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox