From: Nikolay Borisov <kernel@kyup.com>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Cc: Jan Kara <jack@suse.com>, Theodore Ts'o <tytso@mit.edu>
Subject: sleeping function called in atomic
Date: Tue, 18 Oct 2016 15:33:19 +0300 [thread overview]
Message-ID: <5806168F.2010708@kyup.com> (raw)
Hello,
I've been seeing the following splat ever since 4.8-rc1:
[ 2.795057] BUG: sleeping function called from invalid context at ./include/linux/buffer_head.h:358
[ 2.796742] in_atomic(): 1, irqs_disabled(): 0, pid: 993, name: mount
[ 2.797966] CPU: 0 PID: 993 Comm: mount Not tainted 4.9.0-rc1-clouder1 #62
[ 2.798952] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.1-0-g4adadbd-20150316_085822-nilsson.home.kraxel.org 04/01/2014
[ 2.798952] ffff880006423548 ffffffff81318c89 ffffffff819ecdd0 0000000000000166
[ 2.798952] ffff880006423558 ffffffff810810b0 ffff880006423580 ffffffff81081153
[ 2.798952] ffff880006e5a1a0 ffff88000690e400 0000000000000000 ffff8800064235c0
[ 2.798952] Call Trace:
[ 2.798952] [<ffffffff81318c89>] dump_stack+0x67/0x9e
[ 2.798952] [<ffffffff810810b0>] ___might_sleep+0xf0/0x140
[ 2.798952] [<ffffffff81081153>] __might_sleep+0x53/0xb0
[ 2.798952] [<ffffffff8126c1dc>] ext4_commit_super+0x19c/0x290
[ 2.798952] [<ffffffff8126e61a>] __ext4_grp_locked_error+0x14a/0x230
[ 2.798952] [<ffffffff81081153>] ? __might_sleep+0x53/0xb0
[ 2.798952] [<ffffffff812822be>] ext4_mb_generate_buddy+0x1de/0x320
[ 2.798952] [<ffffffff812828ca>] ext4_mb_init_cache+0x3aa/0x740
[ 2.798952] [<ffffffff81282e15>] ext4_mb_init_group+0x1b5/0x240
[ 2.798952] [<ffffffff8128300f>] ext4_mb_good_group+0x16f/0x190
[ 2.798952] [<ffffffff81285c68>] ext4_mb_regular_allocator+0x288/0x450
[ 2.798952] [<ffffffff812877d8>] ext4_mb_new_blocks+0x508/0xb40
[ 2.798952] [<ffffffff81277fe1>] ? ext4_find_extent+0x1f1/0x2f0
[ 2.798952] [<ffffffff81277fe1>] ? ext4_find_extent+0x1f1/0x2f0
[ 2.798952] [<ffffffff8127c294>] ext4_ext_map_blocks+0x964/0x1ca0
[ 2.798952] [<ffffffff8114bb56>] ? release_pages+0x2a6/0x330
[ 2.798952] [<ffffffff8113af4e>] ? find_get_pages_tag+0x11e/0x280
[ 2.798952] [<ffffffff8124d50e>] ext4_map_blocks+0x10e/0x640
[ 2.798952] [<ffffffff81250d86>] ? ext4_writepages+0x436/0xd90
[ 2.798952] [<ffffffff8125101a>] ext4_writepages+0x6ca/0xd90
[ 2.798952] [<ffffffff81081153>] ? __might_sleep+0x53/0xb0
[ 2.798952] [<ffffffff81259ccc>] ? ext4_find_entry+0x24c/0x6a0
[ 2.798952] [<ffffffff81149f1e>] do_writepages+0x1e/0x30
[ 2.798952] [<ffffffff8113c31a>] __filemap_fdatawrite_range+0xaa/0xf0
[ 2.798952] [<ffffffff8113c40c>] filemap_flush+0x1c/0x20
[ 2.798952] [<ffffffff8124e68c>] ext4_alloc_da_blocks+0x2c/0x80
[ 2.798952] [<ffffffff8125d68d>] ext4_rename+0x62d/0x8a0
[ 2.798952] [<ffffffff811c2ffd>] ? terminate_walk+0x6d/0xe0
[ 2.798952] [<ffffffff8125d91d>] ext4_rename2+0x1d/0x30
[ 2.798952] [<ffffffff811c5d3e>] vfs_rename+0x5de/0x840
[ 2.798952] [<ffffffff811cae68>] SyS_rename+0x398/0x3b0
[ 2.798952] [<ffffffff8166bb6e>] entry_SYSCALL_64_fastpath+0x1c/0xac
This complains due to the lock_buffer(sbh); being called in ext4_commit_super.
This happens while booting on a KVM instance.
next reply other threads:[~2016-10-18 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 12:33 Nikolay Borisov [this message]
2016-10-18 14:12 ` sleeping function called in atomic Theodore Ts'o
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=5806168F.2010708@kyup.com \
--to=kernel@kyup.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.