All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [2.6.19-rc4] "possible recursive locking detected" in reiserfs_xattr_set
Date: Fri, 03 Nov 2006 17:12:20 +0100	[thread overview]
Message-ID: <454B6A64.1000107@imap.cc> (raw)

[-- Attachment #1: Type: text/plain, Size: 4294 bytes --]

JFTR, these messages still appear with 2.6.19-rc4:

Nov  3 11:08:05 gx110 kernel: [ 1025.512025]
Nov  3 11:08:05 gx110 kernel: [ 1025.512031] =============================================
Nov  3 11:08:05 gx110 kernel: [ 1025.512053] [ INFO: possible recursive locking detected ]
Nov  3 11:08:05 gx110 kernel: [ 1025.512064] 2.6.19-rc4-noinitrd #1
Nov  3 11:08:05 gx110 kernel: [ 1025.512071] ---------------------------------------------
Nov  3 11:08:05 gx110 kernel: [ 1025.512080] kdm/3234 is trying to acquire lock:
Nov  3 11:08:05 gx110 kernel: [ 1025.512089]  (&inode->i_mutex){--..}, at: [<c035aced>] mutex_lock+0x1c/0x1f
Nov  3 11:08:05 gx110 kernel: [ 1025.512124]
Nov  3 11:08:05 gx110 kernel: [ 1025.512126] but task is already holding lock:
Nov  3 11:08:05 gx110 kernel: [ 1025.512134]  (&inode->i_mutex){--..}, at: [<c035aced>] mutex_lock+0x1c/0x1f
Nov  3 11:08:05 gx110 kernel: [ 1025.512152]
Nov  3 11:08:05 gx110 kernel: [ 1025.512155] other info that might help us debug this:
Nov  3 11:08:05 gx110 kernel: [ 1025.512165] 3 locks held by kdm/3234:
Nov  3 11:08:05 gx110 kernel: [ 1025.512172]  #0:  (&inode->i_mutex){--..}, at: [<c035aced>] mutex_lock+0x1c/0x1f
Nov  3 11:08:05 gx110 kernel: [ 1025.512192]  #1:  (&REISERFS_I(inode)->xattr_sem){----}, at: [<c01c3951>] reiserfs_acl_chmod+0xe1/0x180
Nov  3 11:08:05 gx110 kernel: [ 1025.512234]  #2:  (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<c01c3986>] reiserfs_acl_chmod+0x116/0x180
Nov  3 11:08:05 gx110 kernel: [ 1025.512257]
Nov  3 11:08:05 gx110 kernel: [ 1025.512260] stack backtrace:
Nov  3 11:08:05 gx110 kernel: [ 1025.512274]  [<c0103dc4>] dump_trace+0x64/0x1cc
Nov  3 11:08:05 gx110 kernel: [ 1025.512300]  [<c0103f45>] show_trace_log_lvl+0x19/0x2e
Nov  3 11:08:05 gx110 kernel: [ 1025.512317]  [<c01042a2>] show_trace+0x12/0x14
Nov  3 11:08:05 gx110 kernel: [ 1025.512334]  [<c01042bb>] dump_stack+0x17/0x19
Nov  3 11:08:05 gx110 kernel: [ 1025.512348]  [<c012fdd9>] __lock_acquire+0x106/0x99c
Nov  3 11:08:05 gx110 kernel: [ 1025.512373]  [<c0130930>] lock_acquire+0x5b/0x7b
Nov  3 11:08:05 gx110 kernel: [ 1025.512457]  [<c035ab5d>] __mutex_lock_slowpath+0xc6/0x23a
Nov  3 11:08:05 gx110 kernel: [ 1025.512482]  [<c035aced>] mutex_lock+0x1c/0x1f
Nov  3 11:08:05 gx110 kernel: [ 1025.512504]  [<c01c29c5>] reiserfs_xattr_set+0xe4/0x2bf
Nov  3 11:08:05 gx110 kernel: [ 1025.512529]  [<c01c33ef>] reiserfs_set_acl+0x18d/0x204
Nov  3 11:08:05 gx110 kernel: [ 1025.512553]  [<c01c3994>] reiserfs_acl_chmod+0x124/0x180
Nov  3 11:08:05 gx110 kernel: [ 1025.512577]  [<c01a3c41>] reiserfs_setattr+0x20b/0x243
Nov  3 11:08:05 gx110 kernel: [ 1025.512608]  [<c017395b>] notify_change+0x135/0x2c2
Nov  3 11:08:05 gx110 kernel: [ 1025.512645]  [<c015fbba>] sys_fchmodat+0xa0/0xca
Nov  3 11:08:05 gx110 kernel: [ 1025.512670]  [<c015fc05>] sys_chmod+0x21/0x23
Nov  3 11:08:05 gx110 kernel: [ 1025.512691]  [<c0102dfd>] sysenter_past_esp+0x56/0x8d
Nov  3 11:08:05 gx110 kernel: [ 1025.512718] DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
Nov  3 11:08:05 gx110 kernel: [ 1025.512733]
Nov  3 11:08:05 gx110 kernel: [ 1025.512746] Leftover inexact backtrace:
Nov  3 11:08:05 gx110 kernel: [ 1025.512750]
Nov  3 11:08:05 gx110 kernel: [ 1025.512771]  =======================

The message appears when the first KDE session is started.

Possibly relevant system info:

ts@gx110:~> uname -a
Linux gx110 2.6.19-rc4-noinitrd #1 PREEMPT Fri Nov 3 02:47:33 CET 2006 i686 i686 i386 GNU/Linux
ts@gx110:~> fgrep REISER /boot/config-2.6.19-rc4-noinitrd
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
ts@gx110:~> mount
/dev/hda3 on / type reiserfs (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hda1 on /windows/C type ntfs (ro)
/dev/hda4 on /windows/D type vfat (rw)
usbfs on /proc/bus/usb type usbfs (rw)

HTH

-- 
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeoeffnet mindestens haltbar bis: (siehe Rueckseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

             reply	other threads:[~2006-11-03 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 16:12 Tilman Schmidt [this message]
2006-11-06  9:18 ` [PATCH] Re:[2.6.19-rc4] "possible recursive locking detected" in reiserfs_xattr_set Srinivasa Ds
2006-11-06 19:19   ` Tilman Schmidt
2006-11-07 12:52     ` Srinivasa Ds
2006-11-08  0:04       ` Tilman Schmidt

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=454B6A64.1000107@imap.cc \
    --to=tilman@imap.cc \
    --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 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.