From: Jan De Luyck <ml_linuxkernel_20060528@kcore.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.18.1] possible recursive locking detected
Date: Thu, 2 Nov 2006 15:04:23 +0100 [thread overview]
Message-ID: <200611021504.23384.ml_linuxkernel_20060528@kcore.org> (raw)
After rebuilding my kernel today to enable as much
debugging options as possible in an attempt to try to debug
a full system freeze I'm seeing, I saw this in the log.
No idea if it's bad or not, so I'll report it here.
Nov 2 11:05:48 rutabaga kernel: =============================================
Nov 2 11:05:48 rutabaga kernel: [ INFO: possible recursive locking detected ]
Nov 2 11:05:48 rutabaga kernel: ---------------------------------------------
Nov 2 11:05:48 rutabaga kernel: mount/1942 is trying to acquire lock:
Nov 2 11:05:48 rutabaga kernel: (&(&ip->i_lock)->mr_lock){----}, at: [<c01f76be>] xfs_ilock+0x7e/0xa0
Nov 2 11:05:48 rutabaga kernel:
Nov 2 11:05:48 rutabaga kernel: but task is already holding lock:
Nov 2 11:05:48 rutabaga kernel: (&(&ip->i_lock)->mr_lock){----}, at: [<c01f76be>] xfs_ilock+0x7e/0xa0
Nov 2 11:05:48 rutabaga kernel:
Nov 2 11:05:48 rutabaga kernel: other info that might help us debug this:
Nov 2 11:05:48 rutabaga kernel: 2 locks held by mount/1942:
Nov 2 11:05:48 rutabaga kernel: #0: (&inode->i_mutex){--..}, at: [<c035bc85>] mutex_lock+0x25/0x30
Nov 2 11:05:48 rutabaga kernel: #1: (&(&ip->i_lock)->mr_lock){----}, at: [<c01f76be>] xfs_ilock+0x7e/0xa0
Nov 2 11:05:48 rutabaga kernel:
Nov 2 11:05:48 rutabaga kernel: stack backtrace:
Nov 2 11:05:48 rutabaga kernel: [<c0103bf0>] show_trace_log_lvl+0x1b0/0x1d0
Nov 2 11:05:48 rutabaga kernel: [<c010435b>] show_trace+0x1b/0x20
Nov 2 11:05:48 rutabaga kernel: [<c0104444>] dump_stack+0x24/0x30
Nov 2 11:05:48 rutabaga kernel: [<c013465b>] __lock_acquire+0x8db/0xd70
Nov 2 11:05:48 rutabaga kernel: [<c0134e69>] lock_acquire+0x69/0x90
Nov 2 11:05:48 rutabaga kernel: [<c0130b5c>] down_write+0x4c/0x70
Nov 2 11:05:48 rutabaga kernel: [<c01f76be>] xfs_ilock+0x7e/0xa0
Nov 2 11:05:48 rutabaga kernel: [<c01f831c>] xfs_iget+0x41c/0x61a
Nov 2 11:05:48 rutabaga kernel: [<c0212e49>] xfs_trans_iget+0x119/0x190
Nov 2 11:05:48 rutabaga kernel: [<c01fcf70>] xfs_ialloc+0xb0/0x550
Nov 2 11:05:48 rutabaga kernel: [<c0213b28>] xfs_dir_ialloc+0x78/0x2e0
Nov 2 11:05:48 rutabaga kernel: [<c021bceb>] xfs_create+0x39b/0x6f0
Nov 2 11:05:48 rutabaga kernel: [<c022699e>] xfs_vn_mknod+0x2de/0x2f0
Nov 2 11:05:48 rutabaga kernel: [<c0226a05>] xfs_vn_create+0x25/0x30
Nov 2 11:05:48 rutabaga kernel: [<c01710ec>] vfs_create+0x9c/0xf0
Nov 2 11:05:48 rutabaga kernel: [<c01746a2>] open_namei+0x632/0x710
Nov 2 11:05:48 rutabaga kernel: [<c015fb38>] do_filp_open+0x38/0x60
Nov 2 11:05:48 rutabaga kernel: [<c015fbab>] do_sys_open+0x4b/0xf0
Nov 2 11:05:48 rutabaga kernel: [<c015fca7>] sys_open+0x27/0x30
Nov 2 11:05:48 rutabaga kernel: [<c01032e7>] syscall_call+0x7/0xb
Nov 2 11:05:48 rutabaga kernel: [<b7f1eb8d>] 0xb7f1eb8d
Kind regards,
Jan
--
The truth about a woman often lasts longer than the woman is true.
reply other threads:[~2006-11-02 14:06 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=200611021504.23384.ml_linuxkernel_20060528@kcore.org \
--to=ml_linuxkernel_20060528@kcore.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