RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 635762 - GFS2: BUG at fs/gfs2/glock.c:173, inode glock
Summary: GFS2: BUG at fs/gfs2/glock.c:173, inode glock
Keywords:
Status: CLOSED DUPLICATE of bug 635041
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Steve Whitehouse
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-20 16:18 UTC by Nate Straz
Modified: 2011-03-17 19:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-17 19:11:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nate Straz 2010-09-20 16:18:42 UTC 
Description of problem:

I hit another glock.c:173 bug with another kind of glock.  I've hit this previously with an iopen glock (610136) and flock (612608).  This was hit while umounting after the brawl load running on a 1k fsblock file system.

 G:  s:UN n:2/5433cf f:fI t:UN d:EX/0 a:0 r:0
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:173!
invalid opcode: 0000 [#1] SMP 
last sysfs file: /sys/devices/system/cpu/cpu3/cache/index2/shared_cpu_map
CPU 2 
Modules linked in: sctp libcrc32c gfs2 dlm configfs sunrpc cpufreq_ondemand powernow_k8 freq_table ipv6 dm_mirror dm_region_hash dm_log dcdba
s serio_raw k8temp hwmon amd64_edac_mod edac_core edac_mce_amd tg3 sg i2c_piix4 shpchp ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom qla2x
xx scsi_transport_fc scsi_tgt sata_svw ata_generic pata_acpi pata_serverworks radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mod [las
t unloaded: scsi_wait_scan]

Modules linked in: sctp libcrc32c gfs2 dlm configfs sunrpc cpufreq_ondemand powernow_k8 freq_table ipv6 dm_mirror dm_region_hash dm_log dcdba
s serio_raw k8temp hwmon amd64_edac_mod edac_core edac_mce_amd tg3 sg i2c_piix4 shpchp ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom qla2x
xx scsi_transport_fc scsi_tgt sata_svw ata_generic pata_acpi pata_serverworks radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mod [las
t unloaded: scsi_wait_scan]
Pid: 3190, comm: dlm_astd Not tainted 2.6.32-71.el6.x86_64 #1 PowerEdge SC1435
RIP: 0010:[<ffffffffa03fd710>]  [<ffffffffa03fd710>] gfs2_glock_hold+0x20/0x30 [gfs2]
RSP: 0018:ffff880119cede10  EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8801048f7620 RCX: 00000000000029ce
RDX: 0000000000000000 RSI: 0000000000000046 RDI: 0000000000000000
RBP: ffff880119cede10 R08: ffffffff818a1d60 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000005 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: ffff88009c2f1000
FS:  00007f339b269740(0000) GS:ffff880028280000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00000033036d4650 CR3: 00000001e35cd000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process dlm_astd (pid: 3190, threadinfo ffff880119cec000, task ffff880118820080)
Stack:
 ffff880119cede40 ffffffffa03fe1d1 0000000000000001 0000000000000000
<0> 0000000000000001 ffff88010c0a0000 ffff880119cede60 ffffffffa041bbdd
<0> ffff880119cede60 ffff8801048d6c40 ffff880119cedee0 ffffffffa03c13dd
Call Trace:
 [<ffffffffa03fe1d1>] gfs2_glock_complete+0x31/0xd0 [gfs2]
 [<ffffffffa041bbdd>] gdlm_ast+0xfd/0x110 [gfs2]
 [<ffffffffa03c13dd>] dlm_astd+0x25d/0x2b0 [dlm]
 [<ffffffffa041b9e0>] ? gdlm_bast+0x0/0x50 [gfs2]
 [<ffffffffa041bae0>] ? gdlm_ast+0x0/0x110 [gfs2]
 [<ffffffffa03c1180>] ? dlm_astd+0x0/0x2b0 [dlm]
 [<ffffffff81091936>] kthread+0x96/0xa0
 [<ffffffff810141ca>] child_rip+0xa/0x20
 [<ffffffff810918a0>] ? kthread+0x0/0xa0
 [<ffffffff810141c0>] ? child_rip+0x0/0x20
Code: ff ff c9 c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 1f 44 00 00 8b 47 28 85 c0 74 06 f0 ff 47 28 c9 c3 48 89 fe 31 ff e8 a0 fc ff ff <0f> 0
b eb fe 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 48 
RIP  [<ffffffffa03fd710>] gfs2_glock_hold+0x20/0x30 [gfs2]
 RSP <ffff880119cede10>


Version-Release number of selected component (if applicable):
kernel-2.6.32-71.el6.x86_64

How reproducible:
Unknown

Actual results:
kernel BUG() and panic

Expected results:
No kernel BUG() nor panic.

Additional info:
Comment 2 Steve Whitehouse 2010-09-22 12:58:51 UTC 
Maybe a dup of bz #635041

We thought that the issue with dlm providing out of order replies had been fixed, but the traces in that bug indicate that it is still possible.
Comment 3 RHEL Program Management 2011-01-07 04:14:08 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 Suzanne Logcher 2011-01-07 16:19:47 UTC 
This request was erroneously denied for the current release of Red Hat
Enterprise Linux.  The error has been fixed and this request has been
re-proposed for the current release.
Comment 5 RHEL Program Management 2011-02-01 05:45:50 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6 RHEL Program Management 2011-02-01 18:43:30 UTC 
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.
Comment 7 Steve Whitehouse 2011-03-09 12:25:25 UTC 
This is quite likely to be a dup of bug #653041, also the code in gfs2 which deals with freeing glocks has been changed by bug #656939 and bug #682951 such that it is pretty unlikely that this report would still be relevant after those fixes.

Unless this can be reproduced after the three patches I just mentioned, I'd suggest closing this as a dup of #635041.
Comment 8 Ric Wheeler 2011-03-17 19:11:37 UTC 
Closing as a duplicate - please reopen if it pops up again.

*** This bug has been marked as a duplicate of bug 635041 ***
Note You need to log in before you can comment on or make changes to this bug.