[Bugme-new] [Bug 9264] New: leds: ledtrig-timer calls sleeping function from invalid context

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=9264

           Summary: leds: ledtrig-timer calls sleeping function from invalid
                    context
           Product: Drivers
           Version: 2.5
     KernelVersion: 2.6.24-rc1
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
        AssignedTo: drivers_other at kernel-bugs.osdl.org
        ReportedBy: nm127 at freemail.hu


Most recent kernel where this bug did not occur: -
Distribution: Debian 4.0
Hardware Environment: Clevo D410J
Software Environment:
Problem Description:

When I activate and deactivate the ledtrig-timer module for a LED I get the
following BUG message in dmesg:

When activating:

BUG: sleeping function called from invalid context at mm/slab.c:3050
in_atomic():1, irqs_disabled():0
3 locks held by bash/3557:
 #0:  (&buffer->mutex){--..}, at: [<c01b4f3b>] sysfs_write_file+0x2b/0x100
 #1:  (triggers_list_lock){----}, at: [<c0296efa>] led_trigger_store+0x7a/0x110
 #2:  (&led_cdev->trigger_lock){--..}, at: [<c0296f5c>]
led_trigger_store+0xdc/0x110
 [<c010533a>] show_trace_log_lvl+0x1a/0x30
 [<c0105d32>] show_trace+0x12/0x20
 [<c0105e85>] dump_stack+0x15/0x20
 [<c011a478>] __might_sleep+0xb8/0xd0
 [<c01749cf>] kmem_cache_alloc+0xcf/0x120
 [<c01b5ac4>] sysfs_new_dirent+0x34/0x100
 [<c01b52cf>] sysfs_add_file+0x2f/0x90
 [<c01b535c>] sysfs_create_file+0x2c/0x40
 [<c0278efd>] device_create_file+0x2d/0x50
 [<f8d0314a>] timer_trig_activate+0x4a/0xa0 [ledtrig_timer]
 [<c0296a09>] led_trigger_set+0xa9/0xd0
 [<c0296f65>] led_trigger_store+0xe5/0x110
 [<c027839f>] dev_attr_store+0x2f/0x40
 [<c01b4fb2>] sysfs_write_file+0xa2/0x100
 [<c0177ff9>] vfs_write+0x99/0x130
 [<c01785dd>] sys_write+0x3d/0x70
 [<c01042d2>] sysenter_past_esp+0x5f/0xa5
 =======================

When deactivating:

BUG: sleeping function called from invalid context at kernel/mutex.c:207
in_atomic():1, irqs_disabled():0
2 locks held by bash/3557:
 #0:  (&buffer->mutex){--..}, at: [<c01b4f3b>] sysfs_write_file+0x2b/0x100
 #1:  (&led_cdev->trigger_lock){--..}, at: [<c0296ed5>]
led_trigger_store+0x55/0x110
 [<c010533a>] show_trace_log_lvl+0x1a/0x30
 [<c0105d32>] show_trace+0x12/0x20
 [<c0105e85>] dump_stack+0x15/0x20
 [<c011a478>] __might_sleep+0xb8/0xd0
 [<c030306d>] mutex_lock_nested+0x1d/0x2f0
 [<c01b5a1c>] sysfs_addrm_start+0x2c/0xa0
 [<c01b4808>] sysfs_hash_and_remove+0x28/0x70
 [<c01b523d>] sysfs_remove_file+0xd/0x10
 [<c0278ab7>] device_remove_file+0x27/0x40
 [<f8d03023>] timer_trig_deactivate+0x23/0x50 [ledtrig_timer]
 [<c02969ba>] led_trigger_set+0x5a/0xd0
 [<c0296ede>] led_trigger_store+0x5e/0x110
 [<c027839f>] dev_attr_store+0x2f/0x40
 [<c01b4fb2>] sysfs_write_file+0xa2/0x100
 [<c0177ff9>] vfs_write+0x99/0x130
 [<c01785dd>] sys_write+0x3d/0x70
 [<c01042d2>] sysenter_past_esp+0x5f/0xa5


Steps to reproduce:
# modprobe -k ledtrig-timer
# modprobe -k leds-clevo-mail
# echo timer >/sys/class/leds/clevo::mail/trigger 
# echo none >/sys/class/leds/clevo::mail/trigger


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.