Your message dated Wed, 12 May 2010 15:09:15 +0200
with message-id <20100512130915.ga28...@rivendell>
and subject line Non-bug
has caused the Debian Bug report #399432,
regarding dpkg makes 2.6.18.2 kernel send possible recursive locking detected
events
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
399432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399432
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.13.22
Severity: normal
I realise this bug might not be dpkg related but more likely a kernel, and
specifically xfs, problem. I'm sending as a dpkg bug anyway as I only see
these events when running dpkg, and in the hope that you can reproduce it,
and see what part of dpkg is causing it.
I recently recompiled 2.6.18.2 kernel from pristine kernel source. On a
whim I enabled the lock checks from kernel debugging (I don't actually need
it)
A few hours later I got the output below after a dselect->install in the
kernel log. I now have seen these output 3 times, and, as I said above, only
with dpkg.
=============================================
[ INFO: possible recursive locking detected ]
---------------------------------------------
dpkg/2725 is trying to acquire lock:
(&(&ip->i_lock)->mr_lock){----}, at: [<ffffffff88135760>] xfs_ilock+0x58/0x7b
[xfs]
but task is already holding lock:
(&(&ip->i_lock)->mr_lock){----}, at: [<ffffffff88135760>] xfs_ilock+0x58/0x7b
[xfs]
other info that might help us debug this:
3 locks held by dpkg/2725:
#0: (&inode->i_mutex/1){--..}, at: [<ffffffff8023c557>] do_unlinkat+0x7e/0x175
#1: (&inode->i_mutex){--..}, at: [<ffffffff80262765>] mutex_lock+0x25/0x2a
#2: (&(&ip->i_lock)->mr_lock){----}, at: [<ffffffff88135760>]
xfs_ilock+0x58/0x7b [xfs]
stack backtrace:
Call Trace:
[<ffffffff802936a5>] __lock_acquire+0x146/0xa49
[<ffffffff80264110>] _spin_unlock_irq+0x2b/0x57
[<ffffffff88135760>] :xfs:xfs_ilock+0x58/0x7b
[<ffffffff80294023>] lock_acquire+0x7b/0xa1
[<ffffffff88135760>] :xfs:xfs_ilock+0x58/0x7b
[<ffffffff80290f0d>] down_write+0x36/0x42
[<ffffffff88135760>] :xfs:xfs_ilock+0x58/0x7b
[<ffffffff8814e42a>] :xfs:xfs_lock_dir_and_entry+0x8b/0xc6
[<ffffffff88151614>] :xfs:xfs_remove+0x1c0/0x3c1
[<ffffffff8815a135>] :xfs:xfs_vn_unlink+0x26/0x60
[<ffffffff8026270f>] __mutex_lock_slowpath+0x241/0x272
[<ffffffff80239f02>] debug_mutex_free_waiter+0x52/0x56
[<ffffffff80262733>] __mutex_lock_slowpath+0x265/0x272
[<ffffffff8024a040>] vfs_unlink+0xcd/0x114
[<ffffffff8023c5a0>] do_unlinkat+0xc7/0x175
[<ffffffff802635b9>] trace_hardirqs_on_thunk+0x35/0x37
[<ffffffff802931fb>] trace_hardirqs_on+0x107/0x131
[<ffffffff802635b9>] trace_hardirqs_on_thunk+0x35/0x37
[<ffffffff802b55c4>] sys_unlink+0x11/0x13
[<ffffffff8025d38e>] system_call+0x7e/0x83
/ (and /var) is ext3
/usr is using xfs
Cheers,
Ernest ter Kuile.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.2
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages dpkg depends on:
ii coreutils 5.97-5 The GNU core utilities
ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries
dpkg recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
as you said yourself, this is clearly not a dpkg bug but a kernel bug.
Unfortunately the kernel 2.6.18 is no longer supported by Debian so I
can't reassign the bug. Thus I'm closing it.
And chances are that the xfs bug has been solved in the mean time.
Cheers,
--
Raphaƫl Hertzog
Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/
My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/
--- End Message ---