Bug 3986 - EIP in locks_remove_flock: invalid operand
Summary: EIP in locks_remove_flock: invalid operand
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Memory Management
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Andrew Morton
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-03 16:17 UTC by Russ Woodman
Modified: 2006-08-03 16:04 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.8
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Russ Woodman 2005-01-03 16:17:59 UTC
Distribution:  Debian Sid

Hardware Environment:  Intel N440BX mobo with 2 PII-450 processors, 512MB RAM,
9GB SCSI-2 drive

Software Environment:  FreeRADIUS process involved in fault, SMP kernel under
Debian GNU/Linux 3.1 (Sid)

Problem Description:

Jan  3 15:04:33 natco1 kernel: ------------[ cut here ]------------
Jan  3 15:04:33 natco1 kernel: kernel BUG at fs/locks.c:1726!
Jan  3 15:04:33 natco1 kernel: invalid operand: 0000 [#1]
Jan  3 15:04:33 natco1 kernel: PREEMPT SMP
Jan  3 15:04:33 natco1 kernel: Modules linked in: nfsd exportfs lockd sunrpc
iptable_filter ip_tables ipv6 capability commoncap eepro100 mii usbkbd usbcore
rtc ext3 jbd mbcache sd_mod sym53c8xx scsi_transport_spi scsi_mod unix font
vesafb cfbcopyarea cfbimgblt cfbfillrect
Jan  3 15:04:33 natco1 kernel: CPU:    1
Jan  3 15:04:33 natco1 kernel: EIP:    0060:[locks_remove_flock+193/256]    Not
tainted
Jan  3 15:04:33 natco1 kernel: EFLAGS: 00010246   (2.6.8-1-686-smp)
Jan  3 15:04:33 natco1 kernel: EIP is at locks_remove_flock+0xc1/0x100
Jan  3 15:04:33 natco1 kernel: eax: dd53cc6c   ebx: ddfedea4   ecx: dd53c96c  
edx: 00000001
Jan  3 15:04:33 natco1 kernel: esi: ddfede08   edi: d6f749c0   ebp: ddfede08  
esp: cf86ff68
Jan  3 15:04:33 natco1 kernel: ds: 007b   es: 007b   ss: 0068
Jan  3 15:04:33 natco1 kernel: Process freeradius (pid: 2037,
threadinfo=cf86e000 task=de23e7d0)
Jan  3 15:04:33 natco1 kernel: Stack: 00000000 00000000 d6f749c0 00000000
dfb1e4a0 c0160ae0 d6f749c0 d6f749c0
Jan  3 15:04:33 natco1 kernel:        c746fa00 d6f749c0 00000000 00000006
464fd7c4 c0174379 00000008 00000006
Jan  3 15:04:33 natco1 kernel:        464fd7c4 d6f749c0 00000008 464fd7c4
401d4fcc cf86e000 c01061fb 00000008
Jan  3 15:04:33 natco1 kernel: Call Trace:
Jan  3 15:04:33 natco1 kernel:  [__fput+48/320] __fput+0x30/0x140
Jan  3 15:04:33 natco1 kernel:  [sys_fcntl64+121/192] sys_fcntl64+0x79/0xc0
Jan  3 15:04:33 natco1 kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Jan  3 15:04:33 natco1 kernel: Code: 0f 0b be 06 0b 1b 2b c0 eb 9a 89 1c 24 b9
02 00 00 00 89 4c

Steps to reproduce:  Unknown
Comment 1 Adrian Bunk 2006-01-16 11:18:13 UTC
Is this issue still present in kernel 2.6.15?
Comment 2 Akshat Aranya 2006-04-14 12:36:25 UTC
This bug happened for me over NFS too.

Hardware Environment:  2-Dual core AMD Opteron , 4GB RAM
Software Environment:  RHEL 4 SMP kernel.  Process g++ while trying to write
over NFS.

Problem Description:

Apr 14 15:10:21 hfs12 kernel: kernel BUG at fs/locks.c:1799!
Apr 14 15:10:21 hfs12 kernel: invalid operand: 0000 [#1]
Apr 14 15:10:21 hfs12 kernel: SMP
Apr 14 15:10:21 hfs12 kernel: Modules linked in: nfsd exportfs parport_pc lp
parport autofs4 i2c_dev i2c_core nfs lockd nfs_acl sunrpc dm_mirror dm_mod
button battery ac md5 ipv6 ohci_hcd hw_random e100 mii tg3 floppy ext3 jbd raid0
sata_sil libata sd_mod scsi_mod
Apr 14 15:10:21 hfs12 kernel: CPU:    1
Apr 14 15:10:21 hfs12 kernel: EIP:    0060:[<c016dd4c>]    Not tainted VLI
Apr 14 15:10:21 hfs12 kernel: EFLAGS: 00010246   (2.6.9-34.ELsmp)
Apr 14 15:10:21 hfs12 kernel: EIP is at locks_remove_flock+0xa1/0xe1
Apr 14 15:10:21 hfs12 kernel: eax: f64efa8c   ebx: f5be620c   ecx: 00000000  
edx: 00000081
Apr 14 15:10:21 hfs12 kernel: esi: 00000000   edi: f5be6164   ebp: f58c06c0  
esp: f40b3f2c
Apr 14 15:10:21 hfs12 kernel: ds: 007b   es: 007b   ss: 0068
Apr 14 15:10:21 hfs12 kernel: Process g++-4.0 (pid: 14863, threadinfo=f40b3000
task=f36ef830)
Apr 14 15:10:21 hfs12 kernel: Stack: f58c06c0 f896643a f40b3f44 f8966e2a
f8c3abd7 c016dca4 f40b3f6c 00000001
Apr 14 15:10:21 hfs12 kernel:        00000000 00000001 f5be60f8 f378c3c0
00003a0f f8c426ac 00000000 ffffffff
Apr 14 15:10:21 hfs12 kernel:        f6020f40 f58c06c0 00000201 00000000
00000000 00000246 00000000 f58c06c0
Apr 14 15:10:21 hfs12 kernel: Call Trace:
Apr 14 15:10:21 hfs12 kernel:  [<f896643a>] nlm_put_lockowner+0x11/0x49 [lockd]
Apr 14 15:10:21 hfs12 kernel:  [<f8966e2a>]
nlmclnt_locks_release_private+0xb/0x14 [lockd]
Apr 14 15:10:21 hfs12 kernel:  [<f8c3abd7>] nfs_lock+0x0/0xc7 [nfs]
Apr 14 15:10:21 hfs12 kernel:  [<c016dca4>] locks_remove_posix+0x130/0x137
Apr 14 15:10:21 hfs12 kernel:  [<f8c426ac>] nfs_wait_on_requests+0x7e/0xba [nfs]
Apr 14 15:10:21 hfs12 kernel:  [<c015b0c6>] __fput+0x41/0x100
Apr 14 15:10:21 hfs12 kernel:  [<c0159d21>] filp_close+0x59/0x5f
Apr 14 15:10:21 hfs12 kernel:  [<c02d2657>] syscall_call+0x7/0xb
Apr 14 15:10:21 hfs12 kernel: Code: 38 39 68 2c 75 2d 0f b6 50 30 f6 c2 02 74 09
89 d8 e8 b3 df ff ff eb 1d f6 c2 20 74 0e ba 02 00 00 00 89 d8 e8 ce ec ff ff eb
0a <0f> 0b 07 07 6c 74 2e c0 89 c3 8b 03 eb c4 b8 00 f0 ff ff 21 e0
Apr 14 15:10:21 hfs12 kernel:  <0>Fatal exception: panic in 5 seconds


Comment 3 Andrew Morton 2006-04-14 12:54:33 UTC
2.6.9 is awfully old.  This might well have been fixed in the intervening
year or two.  It would be more appropriate to take this up with Red Hat,
sorry.
Comment 4 Adrian Bunk 2006-04-14 12:57:31 UTC
Does it still occur with kernel 2.6.16.5?

Otherwise (as Andrew already said), please contact RedHat for support with this
issue.
Comment 5 Adrian Bunk 2006-08-03 16:04:42 UTC
Please reopen this bug if it is still present in kernel 2.6.17.

Note You need to log in before you can comment on or make changes to this bug.