From: Jens Axboe <jens.axboe@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, jurriaan <thunder7@xs4all.nl>,
linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: 2.6.27-rc4: lots of 'in_atomic():1, irqs_disabled():0' with software-raid1
Date: Thu, 28 Aug 2008 09:48:30 +0200 [thread overview]
Message-ID: <20080828074830.GV20055@kernel.dk> (raw)
In-Reply-To: <20080828004532.45d8b8c9.akpm@linux-foundation.org>
On Thu, Aug 28 2008, Andrew Morton wrote:
> On Thu, 28 Aug 2008 09:33:24 +0200 Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > On Wed, Aug 27 2008, Rafael J. Wysocki wrote:
> > > [Adding CCs]
> > >
> > > On Wednesday, 27 of August 2008, jurriaan wrote:
> > > > After returning from my holidays, I proceeded to test 2.6.27-rc4. 2.6.26
> > > > works fine, but 2.6.27-rc4 gives me lots of:
> > > >
> > > > Aug 27 18:03:10 middle kernel: in_atomic():1, irqs_disabled():0
> > > > Aug 27 18:03:10 middle kernel: Pid: 1185, comm: md2_raid1 Not tainted 2.6.27-rc4 #2
> > > > Aug 27 18:03:10 middle kernel:
> > > > Aug 27 18:03:10 middle kernel: Call Trace:
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff802303fb>] __might_sleep+0xdb/0x100
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff802734a9>] mempool_alloc+0x89/0x140
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff802c8deb>] bio_alloc_bioset+0x2b/0xb0
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff802c8ed0>] bio_alloc+0x10/0x20
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8061ecda>] md_super_write+0x3a/0xe0
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80623e0e>] write_page+0x14e/0x310
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff803a30f1>] ? rb_insert_color+0x101/0x130
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8022de7f>] ? update_curr+0x3f/0x60
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8039e3e9>] ? __next_cpu+0x19/0x30
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80231ecc>] ? find_busiest_group+0x1dc/0x960
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff806240ab>] bitmap_update_sb+0xdb/0x110
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8061ef65>] md_update_sb+0x1e5/0x370
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80620dc5>] md_check_recovery+0x355/0x640
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80607665>] raid1d+0x35/0x10a0
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff802360db>] ? finish_task_switch+0x3b/0xc0
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8070ec96>] ? thread_return+0xa3/0x63d
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80710e52>] ? _spin_lock_irqsave+0x22/0x50
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80247406>] ? lock_timer_base+0x36/0x70
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff807110c2>] ? _spin_unlock_irqrestore+0x12/0x40
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8024749a>] ? try_to_del_timer_sync+0x5a/0x70
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff802474ca>] ? del_timer_sync+0x1a/0x30
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80710e52>] ? _spin_lock_irqsave+0x22/0x50
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff807110c2>] ? _spin_unlock_irqrestore+0x12/0x40
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8061e084>] md_thread+0x54/0x140
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80253390>] ? autoremove_wake_function+0x0/0x40
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8061e030>] ? md_thread+0x0/0x140
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80252fc9>] kthread+0x49/0x80
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8020ca09>] child_rip+0xa/0x11
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff80252f80>] ? kthread+0x0/0x80
> > > > Aug 27 18:03:10 middle kernel: [<ffffffff8020c9ff>] ? child_rip+0x0/0x11
> > > > Aug 27 18:03:10 middle kernel:
> > > >
> > > > I was able to reboot into 2.6.26 without further trouble. I wasn't able
> > > > to find this reported earlier on lkml.
> >
> > Hmm, this just looks like a GFP_NOIO alloc inside rcu_read_lock(), I
> > don't see anything wrong with that?
> >
>
> Cant sleep inside rcu_read_lock(), with CONFIG_PREEMPT_RCU=n, at least.
>
> Dunno if it's legal if CONFIG_PREEMPT_RCU=y. Hopefully not - that
> would be insane. But I've failed to keep up with rcu goings-on
> recently.
Doh right, we of course can't block inside a RCU section. Then
bitmap.c:write_sb_page() wants fixing:
rcu_read_lock();
rdev_for_each_rcu(...)
md_super_write(...)
bio_alloc(GFP_NOIO, 1);
Neil?
--
Jens Axboe
next prev parent reply other threads:[~2008-08-28 7:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 17:05 2.6.27-rc4: lots of 'in_atomic():1, irqs_disabled():0' with software-raid1 jurriaan
2008-08-27 21:47 ` Rafael J. Wysocki
2008-08-28 7:33 ` Jens Axboe
2008-08-28 7:45 ` Andrew Morton
2008-08-28 7:48 ` Jens Axboe [this message]
2008-08-28 7:56 ` Andre Noll
2008-08-28 8:11 ` Jens Axboe
2008-08-28 8:04 ` Andre Noll
2008-08-28 8:27 ` Neil Brown
2008-08-28 8:36 ` Jens Axboe
2008-08-28 9:00 ` Andrew Morton
2008-08-29 7:36 ` Neil Brown
2008-08-29 7:47 ` Jens Axboe
2008-08-29 8:14 ` Andrew Morton
2008-08-29 5:44 ` Neil Brown
2008-08-29 5:48 ` Neil Brown
2008-08-29 7:11 ` Jens Axboe
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=20080828074830.GV20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rjw@sisk.pl \
--cc=thunder7@xs4all.nl \
/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