From: Andrew Morton <akpm@osdl.org>
To: k.gavrilenko@arhont.com
Cc: mlists@arhont.com, linux-kernel@vger.kernel.org,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: 2.6.5-mm6 reiserfs and hpt366 problems
Date: Fri, 16 Apr 2004 16:37:03 -0700 [thread overview]
Message-ID: <20040416163703.36a89df4.akpm@osdl.org> (raw)
In-Reply-To: <408057A5.6010604@arhont.com>
Konstantin Gavrilenko <mlists@arhont.com> wrote:
>
> Apr 16 22:45:06 filo kernel: Debug: sleeping function called from
> invalid context at drivers/block/ll_rw_blk.c:1156
> Apr 16 22:45:06 filo kernel: in_atomic():0, irqs_disabled():1
> Apr 16 22:45:06 filo kernel: Call Trace:
> Apr 16 22:45:06 filo kernel: [<c0117449>] __might_sleep+0x99/0xb0
> Apr 16 22:45:06 filo kernel: [<c02950bf>] generic_unplug_device+0x1f/0x60
> Apr 16 22:45:06 filo kernel: [<c02d9fc9>] unplug_slaves+0x69/0x70
Ah, I see it. There are several instances of unplug_slaves(). The one in
raid1.c is incorrectly calling ->unplug_fn() under spin_lock_irq().
prev parent reply other threads:[~2004-04-16 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 22:01 2.6.5-mm6 reiserfs and hpt366 problems Konstantin Gavrilenko
2004-04-16 22:53 ` Andrew Morton
2004-04-16 23:37 ` Andrew Morton [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=20040416163703.36a89df4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=k.gavrilenko@arhont.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlists@arhont.com \
--cc=neilb@cse.unsw.edu.au \
/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