From: Jeff Mahoney <jeffm@suse.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: kernel BUG at fs/locks.c:1729!
Date: Thu, 08 Apr 2004 14:27:48 -0400 [thread overview]
Message-ID: <407599A4.5090000@suse.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey all -
Ran across this while rebooting a UML instance under 2.6.5; I took a
quick look but was hoping that someone with more familiarity with the
file locking system would be able to notice something more quickly.
To be clear, the BUG was seen on the host kernel, not in the UML kernel.
This is reproducable for me every time I reboot a UML instance; 'halt'
works fine.
The bug occurs when a file is fput for the last time and all the locks
are cleaned up on it. If posix locks remain, it BUGs.
- -Jeff
kernel BUG at fs/locks.c:1729!
invalid operand: 0000 [#1]
SMP
CPU: 1
EIP: 0060:[<c016db0b>] Not tainted
EFLAGS: 00010246 (2.6.5)
EIP is at locks_remove_flock+0x6b/0xc0
eax: f7c08ba0 ebx: f69bdc68 ecx: f66f0000 edx: 00000001
esi: f78ae0e0 edi: f69bdbdc ebp: f66f1e08 esp: f66f1e00
ds: 007b es: 007b ss: 0068
Process linux (pid: 3046, threadinfo=f66f0000 task=f68d3390)
Stack: f78ae0e0 f7fdeee0 f66f1e28 c0159871 f78ae0e0 f6c584a0 f6a08280
f78ae0e0
~ 00000000 f7936a80 f66f1e44 c0156847 f78ae0e0 f7936a80 000060df
0000002b
~ f7936a80 f66f1e64 c01220b7 f78ae0e0 f7936a80 00000002 f793c060
f793c080
Call Trace:
~ [<c0159871>] __fput+0x31/0x120
~ [<c0156847>] filp_close+0x57/0x90
~ [<c01220b7>] put_files_struct+0x67/0xd0
~ [<c01230a7>] do_exit+0x197/0xb80
~ [<c012ab35>] __dequeue_signal+0x155/0x1d0
~ [<c0123acd>] do_group_exit+0x3d/0xc0
~ [<c012d12f>] get_signal_to_deliver+0x28f/0x388
~ [<c0107527>] do_signal+0x87/0x690
~ [<c012c2fc>] specific_send_sig_info+0xcc/0xd0
~ [<c011cd4c>] schedule+0x1ec/0x6d0
~ [<c016989c>] sys_rmdir+0xbc/0x100
~ [<c0107b6b>] do_notify_resume+0x3b/0x40
~ [<c0108386>] work_notifysig+0x13/0x15
Code: 0f 0b c1 06 38 2b 36 c0 eb db b8 00 e0 ff ff 21 e0 8b 10 8b
- --
Jeff Mahoney
SuSE Labs
jeffm@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAdZmkLPWxlyuTD7IRArhgAKCK3gGkKNjIs1992uqrrVNMEiBBdgCgitVl
hVyzL/+KnfsZcjcEOp1VCLo=
=dyJ2
-----END PGP SIGNATURE-----
reply other threads:[~2004-04-08 18:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=407599A4.5090000@suse.com \
--to=jeffm@suse.com \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.