Bug 22782
Summary: | 2.6.36: general protection fault during lockfs lockspace removal | ||
---|---|---|---|
Product: | File System | Reporter: | nik (nik) |
Component: | Other | Assignee: | fs_other |
Status: | RESOLVED OBSOLETE | ||
Severity: | high | CC: | alan, florian, jlbec, maciej.rutecki, rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.36 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 16444 |
Description
nik@linuxbox.cz
2010-11-12 12:05:47 UTC
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Fri, 12 Nov 2010 12:05:49 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=22782 > > Summary: 2.6.36: general protection fault during lockfs > lockspace removal > Product: File System > Version: 2.5 > Kernel Version: 2.6.36 Seems to be a 2.6.35->2.6.36 regression, but nobody has mucked with configfs for a while? > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: high > Priority: P1 > Component: Other > AssignedTo: fs_other@kernel-bugs.osdl.org > ReportedBy: nik@linuxbox.cz > Regression: Yes > > > during lockfs lockspace removal, sometimes GPF occurs: > > general protection fault: 0000 [#1] PREEMPT SMP > last sysfs file: /sys/kernel/dlm/30D118C784964730BDAF2115299250CD/control > CPU 3 > Modules linked in: ocfs2 ocfs2_nodemanager ocfs2_stack_user ocfs2_stackglue > nfs > nfs_acl auth_rpcgss dlm configfs drbd lru_cache cf_conntrack_ipv4 > nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter > ip_tables x_tables bridge stp llc ipv6hc fan battery ac kvm_intel kvm ppdev > parport_pc iTCO_wdt i2c_i801 e1000e video cdc_acm pcspkr i3200_edac edac_core > i2c_core buttlight container thermal output processor thermal_sys sd_mod > crc_t10dif raid1 dm_snapshot dm_zero dm_mirror dm_region_hash dm_log ohci_hcd > ehci_hcd ahci libahci libata scsi_mod [last unloaded: scsi_wait_scan] > > Pid: 8167, comm: dlm_controld.pc Not tainted 2.6.36lb.00_01_PRE11 #1 > X7SBA/X7SBA > RIP: 0010:[<ffffffffa049e0c3>] [<ffffffffa049e0c3>] unlink_group+0x13/0x50 > [configfs] > RSP: 0018:ffff8801259b5dd8 EFLAGS: 00010286 > RAX: ffff000000000000 RBX: 0000000000000008 RCX: 0000000000000000 > RDX: ffffffffa04c3570 RSI: ffff880125a2fd00 RDI: ffff88010200000a > RBP: ffff8801259b5de8 R08: 2222222222222222 R09: 2222222222222222 > R10: 0000000000000000 R11: 2222222222222222 R12: ffff88010200000a > R13: ffff88012afd0948 R14: ffff880125a2fd00 R15: ffff88012a2c1e00 > FS: 00007ff6506d8730(0000) GS:ffff880001b80000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007f63c9959228 CR3: 0000000126baf000 CR4: 00000000000406e0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Process dlm_controld.pc (pid: 8167, threadinfo ffff8801259b4000, task > ffff880125acae60) > Stack: > 0000000000000008 ffff880125a2fd00 ffff8801259b5e08 ffffffffa049e0d5 > <0> 0000000000000000 ffffffffa04c3550 ffff8801259b5e68 ffffffffa049f994 > <0> ffffffffa04c34e0 ffffffffa04c40a0 ffffffffa04c40a0 ffff880114dd9440 > Call Trace: > [<ffffffffa049e0d5>] unlink_group+0x25/0x50 [configfs] > [<ffffffffa049f994>] configfs_rmdir+0x244/0x2e0 [configfs] > [<ffffffff8111f9e0>] vfs_rmdir+0xb0/0x100 > [<ffffffff811219c9>] do_rmdir+0xf9/0x110 > [<ffffffff81111b58>] ? filp_close+0x58/0x90 > [<ffffffff81121a21>] sys_rmdir+0x11/0x20 > [<ffffffff8100242b>] system_call_fastpath+0x16/0x1b > Code: 00 00 48 83 c4 08 5b c9 c3 0f 1f 80 00 00 00 00 0f 1f 84 00 00 00 00 00 > 55 48 89 e5 41 54 49 89 fc 53 48 8b 47 68 48 85 c0 > 00 00 00 e8 db ff ff ff 49 8b 44 > RIP [<ffffffffa049e0c3>] unlink_group+0x13/0x50 [configfs] > RSP <ffff8801259b5dd8> > ---[ end trace e701ef8bbb89eb8e ]--- > On Wednesday, December 08, 2010, Nikola Ciprich wrote:
> AFAIK the problem hasn't been fixed yet..
> n.
>
> On Sun, Dec 05, 2010 at 09:34:33PM +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.35 and 2.6.36.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.35 and 2.6.36. Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=22782
> > Subject : 2.6.36: general protection fault during lockfs
> lockspace removal
> > Submitter : nik@linuxbox.cz <nik@linuxbox.cz>
> > Date : 2010-11-12 12:05 (24 days old)
I don't know how to use the email interface, sorry Andrew. I own configfs, so I'm adding myself to the Cc. I've forwarded it to Dave too, as he owns fs/dlm. Is this still an issue in 2.6.37 or 2.6.38-rc2? |