From: Gerd Knorr <kraxel@bytesex.org>
To: Kernel List <linux-kernel@vger.kernel.org>
Subject: file locking BUG
Date: Fri, 27 Feb 2004 15:37:17 +0100 [thread overview]
Message-ID: <20040227143702.GC15205@bytesex.org> (raw)
Hi,
Got a BUG today. Happened while playing with user-mode-linux, which
uses locks for the image files presenting the virtual hard disks.
The UML kernel complained that it can't lock the disk:
F_SETLK failed, file already locked by pid 24612
Failed to lock '/work/uml/yast2/harddisk.img', err = 11
There is no process (any more) with pid 24612 through. Checked the
kernel log on the host and found the BUG message below ...
Gerd
------------[ cut here ]------------
kernel BUG at fs/locks.c:1727!
invalid operand: 0000 [#2]
CPU: 0
EIP: 0060:[<c016049c>] Tainted: PF
EFLAGS: 00010246
EIP is at locks_remove_flock+0x3c/0x60
eax: f6ea7ea8 ebx: d510cc98 ecx: d510cc14 edx: 00000000
esi: f634d980 edi: d510cc14 ebp: db8dfe80 esp: e97a7f40
ds: 007b es: 007b ss: 0068
Process linux (pid: 24748, threadinfo=e97a6000 task=f649d210)
Stack: f634d980 f7fec700 c014f4a2 f634d980 00000000 c76c5300 00000001 c014ca63
00000f7f 00000009 c76c5300 c011e16f c7158880 c71588a0 f649d210 00000100
c011ee9a c03e1760 c7158880 e77feec0 40001000 c03e1760 00000001 00000000
Call Trace:
[<c014f4a2>] __fput+0x22/0x100
[<c014ca63>] filp_close+0x43/0x70
[<c011e16f>] put_files_struct+0x4f/0xa0
[<c011ee9a>] do_exit+0x14a/0xa10
[<c011f787>] do_group_exit+0x27/0x70
[<c0108e17>] syscall_call+0x7/0xb
Code: 0f 0b bf 06 f5 fb 2f c0 eb da 5b 5e c3 89 d8 e8 d0 fd ff ff
nfs warning: mount version older than kernel
next reply other threads:[~2004-02-27 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 14:37 Gerd Knorr [this message]
2004-03-03 14:55 ` file locking BUG Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040227143702.GC15205@bytesex.org \
--to=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox