Bug 480517

Summary: Trace in cryptsetup after update to kernel 2.6.27.19-3.2
Product: [openSUSE] openSUSE 11.1 Reporter: Forgotten User tmXN95Nddt <forgotten_tmXN95Nddt>
Component: KernelAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: forgotten_tmXN95Nddt
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User tmXN95Nddt 2009-02-27 18:02:40 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6

On x86_64 and x86 machines using openSuse 11.1 i have updated to kernel 2.6.27.19-3.2.

Mounting an encrypted volume at boot time with cryptsetup now gives the following output:

------------[ cut here ]------------
WARNING: at kernel/softirq.c:137 local_bh_enable+0x3c/0x92()
Modules linked in: sha256_generic aes_x86_64 aes_generic cbc usbhid hid ff_memless uhci_hcd dm_crypt crypto_blkcipher loop dm_mod rtc_cmos snd_hda_intel snd_pcm rtc_core snd_timer sr_mod k8temp(N) rtc_lib nvidia(PN) i2c_nforce2 button pcspkr snd_page_alloc forcedeth snd_hwdep i2c_core cdrom snd soundcore sg sd_mod ehci_hcd ohci_hcd crc_t10dif usbcore edd ext3 mbcache jbd fan ide_pci_generic amd74xx ide_core ata_generic pata_amd libata scsi_mod dock thermal processor thermal_sys hwmon
Supported: No
Pid: 1648, comm: cryptsetup Tainted: P          2.6.27.19-3.2-default #1

Call Trace:
 [<ffffffff8020da29>] show_trace_log_lvl+0x41/0x58
 [<ffffffff8049a3da>] dump_stack+0x69/0x6f
 [<ffffffff8023d562>] warn_on_slowpath+0x51/0x77
 [<ffffffff802425b3>] local_bh_enable+0x3c/0x92
 [<ffffffff80433be7>] sk_filter+0x97/0xa0
 [<ffffffff80441a42>] netlink_broadcast+0x220/0x386
 [<ffffffff803614cd>] kobject_uevent_env+0x452/0x520
 [<ffffffff803401d7>] set_disk_ro+0x58/0x8d
 [<ffffffffa0a171d1>] __bind+0x11d/0x136 [dm_mod]
 [<ffffffffa0a1723e>] dm_swap_table+0x54/0x70 [dm_mod]
 [<ffffffffa0a1b766>] do_resume+0xa9/0x122 [dm_mod]
 [<ffffffffa0a1c17d>] ctl_ioctl+0x1cb/0x213 [dm_mod]
 [<ffffffffa0a1c1d3>] dm_ctl_ioctl+0xe/0x12 [dm_mod]
 [<ffffffff802bd249>] vfs_ioctl+0x21/0x6c
 [<ffffffff802bd4b6>] do_vfs_ioctl+0x222/0x231
 [<ffffffff802bd516>] sys_ioctl+0x51/0x73
 [<ffffffff8020bfbb>] system_call_fastpath+0x16/0x1b
 [<00007f7c3dc0eb77>] 0x7f7c3dc0eb77

---[ end trace cde01c702c418d85 ]---

Reproducible: Always

Steps to Reproduce:
1. System using cryptsetup to mount partitions or home directories
2. Update to newest kernel 2.6.27.19-3.2
3. Reboot and error appears
Actual Results:  
I don't know the severity of the bug and what it affected. Volumes seem to mount.
Comment 1 Marcus Meissner 2009-02-28 00:22:36 UTC 
duplicate, thanks for the report!

*** This bug has been marked as a duplicate of bug 479784 ***