linux-kernel - 3.5.1 ext4_ sleeping while atomic bug.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120810031701.GA17765@redhat.com>
Date:	Thu, 9 Aug 2012 23:17:01 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Cc:	tytso@....edu, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org
Subject: 3.5.1 ext4_ sleeping while atomic bug.

BUG: sleeping function called from invalid context at include/linux/buffer_head.h:333
in_atomic(): 1, irqs_disabled(): 0, pid: 9894, name: fstest
3 locks held by fstest/9894:
 #0:  (&type->i_mutex_dir_key#4/1){+.+.+.}, at: [<ffffffff811d5dae>] kern_path_create+0x7e/0x140
 #1:  (&ei->i_data_sem){++++..}, at: [<ffffffff81252e76>] ext4_map_blocks+0xb6/0x250
 #2:  (&(&bgl->locks[i].lock)->rlock){+.+...}, at: [<ffffffff8124a5e7>] ext4_validate_block_bitmap+0x77/0x230
Pid: 9894, comm: fstest Not tainted 3.5.1-1.fc17.x86_64.debug #1
Call Trace:
 [<ffffffff8109cd0a>] __might_sleep+0x18a/0x240
 [<ffffffff811fb430>] __sync_dirty_buffer+0x30/0xf0
 [<ffffffff811fb503>] sync_dirty_buffer+0x13/0x20
 [<ffffffff81273018>] ext4_commit_super+0x1e8/0x260
 [<ffffffff81273283>] save_error_info+0x23/0x30
 [<ffffffff81274539>] __ext4_error+0x89/0xa0
 [<ffffffff8124a5e7>] ? ext4_validate_block_bitmap+0x77/0x230
 [<ffffffff8124a72b>] ext4_validate_block_bitmap+0x1bb/0x230
 [<ffffffff8124b0ae>] ext4_read_block_bitmap_nowait+0x8e/0x3b0
 [<ffffffff812891c0>] ext4_mb_init_cache+0x160/0x990
 [<ffffffff810d16bd>] ? trace_hardirqs_on_caller+0x10d/0x1a0
 [<ffffffff81289b16>] ext4_mb_init_group+0x126/0x250
 [<ffffffff81289d56>] ext4_mb_good_group+0x116/0x130
 [<ffffffff8128c493>] ext4_mb_regular_allocator+0x1a3/0x420
 [<ffffffff811aa920>] ? kmem_cache_alloc+0xe0/0x290
 [<ffffffff8128e2c1>] ext4_mb_new_blocks+0x4f1/0xb90
 [<ffffffff811fad9f>] ? __find_get_block+0xaf/0x220
 [<ffffffff81293e7e>] ext4_alloc_branch+0x42e/0x690
 [<ffffffff816c6030>] ? _raw_spin_unlock_irq+0x30/0x50
 [<ffffffff812949a7>] ext4_ind_map_blocks+0x1e7/0x990
 [<ffffffff816c348a>] ? down_write+0x9a/0xb0
 [<ffffffff81252e76>] ? ext4_map_blocks+0xb6/0x250
 [<ffffffff81252ea5>] ext4_map_blocks+0xe5/0x250
 [<ffffffff8125306b>] ext4_getblk+0x5b/0x1f0
 [<ffffffff81253218>] ext4_bread+0x18/0xa0
 [<ffffffff8125e527>] ext4_mkdir+0x147/0x3d0
 [<ffffffff811d2536>] vfs_mkdir+0xa6/0x130
 [<ffffffff811d6c6e>] sys_mkdirat+0xbe/0xd0
 [<ffffffff811d6c99>] sys_mkdir+0x19/0x20
 [<ffffffff816cefe9>] system_call_fastpath+0x16/0x1b

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/