linux-kernel - BUG: sleeping function called from invalid context at kernel/mutex.c

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 02 Apr 2011 19:47:02 +0800
From:	Xiaotian Feng <dfeng@...hat.com>
To:	tglx@...utronix.de, linux-kernel@...r.kernel.org
CC:	mingo@...e.hu
Subject: BUG: sleeping function called from invalid context at kernel/mutex.c

Hi,

     I've got following warnings when I'm trying to resume from suspend, so
sparse_lock is not safe enough as a mutex for the suspend resume case, can
we simply convert sparse_lock back to spinlock?

BUG: sleeping function called from invalid context at kernel/mutex.c:278
in_atomic(): 1, irqs_disabled(): 1, pid: 2345, name: bash
INFO: lockdep is turned off.
irq event stamp: 0
hardirqs last  enabled at (0): [<          (null)>]           (null)
hardirqs last disabled at (0): [<ffffffff81068391>] 
copy_process+0x4d1/0x1070
softirqs last  enabled at (0): [<ffffffff81068391>] 
copy_process+0x4d1/0x1070
softirqs last disabled at (0): [<          (null)>]           (null)
Pid: 2345, comm: bash Tainted: G          I 2.6.39-rc1+ #59
Call Trace:
  [<ffffffff81052d77>] __might_sleep+0x107/0x140
  [<ffffffff816a57df>] mutex_lock_nested+0x2f/0x50
  [<ffffffff810e191a>] irq_reserve_irqs+0x4a/0xa0
  [<ffffffff810e18a8>] ? __irq_put_desc_unlock+0x28/0x50
  [<ffffffff810e4e78>] irq_set_chip+0x58/0x70
  [<ffffffff810e4fc0>] ? handle_level_irq+0xe0/0xe0
  [<ffffffff810e4eb6>] irq_set_chip_and_handler_name+0x26/0x50
  [<ffffffff8102fbb0>] arch_setup_hpet_msi+0xa0/0xf0
  [<ffffffff8103613c>] hpet_setup_msi_irq+0x1c/0x40
  [<ffffffff81036ad3>] hpet_set_mode+0x1a3/0x1f0
  [<ffffffff81036b34>] hpet_msi_set_mode+0x14/0x20
  [<ffffffff810a03aa>] clockevents_set_mode+0x2a/0x70
  [<ffffffff810a0693>] tick_resume+0x53/0xa0
  [<ffffffff810a0cbd>] tick_notify+0x1cd/0x1e0
  [<ffffffff810a00a8>] ? clockevents_notify+0x28/0x140
  [<ffffffff816ab1f4>] notifier_call_chain+0x94/0xd0
  [<ffffffff810970c6>] raw_notifier_call_chain+0x16/0x20
  [<ffffffff810a00bd>] clockevents_notify+0x3d/0x140
  [<ffffffff8109c000>] timekeeping_resume+0x190/0x1d0
  [<ffffffff813c5fd5>] syscore_resume+0x45/0xf0
  [<ffffffff810bb977>] suspend_enter+0xe7/0x120
  [<ffffffff810bba7e>] suspend_devices_and_enter+0x8e/0x2c0
  [<ffffffff810bbd86>] enter_state+0xd6/0x130
  [<ffffffff810baf99>] state_store+0x99/0x100
  [<ffffffff812c82b7>] kobj_attr_store+0x17/0x20
  [<ffffffff811fc6f3>] sysfs_write_file+0xa3/0x100
  [<ffffffff81187310>] vfs_write+0xd0/0x1a0
  [<ffffffff811874e4>] sys_write+0x54/0xa0
  [<ffffffff816af382>] system_call_fastpath+0x16/0x1b

Thanks
Xiaotian
--
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/