From: Alexander Beregalov <a.beregalov@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs deadlock
Date: Fri, 5 Feb 2010 04:46:38 +0300 [thread overview]
Message-ID: <a4423d671002041746q1d918972i7c180d38a7c1d52@mail.gmail.com> (raw)
In-Reply-To: <20100203225232.GI5068@nowhere>
Hi Frederic
Does it help?
2 locks held by metalog/1558:
#0: (&sb->s_type->i_mutex_key#5){+.+.+.}, at: [<c106a501>]
generic_file_aio_write+0x41/0xb0
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110ed8>]
reiserfs_write_lock_once+0x28/0x50
2 locks held by svscan/1600:
#0: (&sb->s_type->i_mutex_key#5){+.+.+.}, at: [<c10a0112>]
vfs_readdir+0x52/0xa0
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
3 locks held by agetty/1868:
#0: (&p->cred_guard_mutex){+.+.+.}, at: [<c10972f4>]
prepare_bprm_creds+0x24/0x60
#1: (&sb->s_type->i_mutex_key#5){+.+.+.}, at: [<c109a4bb>]
do_lookup+0xbb/0x1c0
#2: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110ed8>]
reiserfs_write_lock_once+0x28/0x50
2 locks held by modprobe/1871:
#0: (&sb->s_type->i_mutex_key#5){+.+.+.}, at: [<c10a0112>]
vfs_readdir+0x52/0xa0
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by fcron/1872:
#0: (&sb->s_type->i_mutex_key#5){+.+.+.}, at: [<c109d903>]
do_filp_open+0x173/0x9f0
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110ed8>]
reiserfs_write_lock_once+0x28/0x50
3 locks held by ddclient/1588:
#0: (&sb->s_type->i_mutex_key#5){+.+.+.}, at: [<c1091417>]
do_truncate+0x57/0x90
#1: (&sb->s_type->i_alloc_sem_key#3){+.+...}, at: [<c10a65e6>]
notify_change+0x1d6/0x330
#2: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110ed8>]
reiserfs_write_lock_once+0x28/0x50
2 locks held by multilog/1615:
#0: (&sb->s_type->i_mutex_key#5){+.+.+.}, at: [<c106a501>]
generic_file_aio_write+0x41/0xb0
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110ed8>]
reiserfs_write_lock_once+0x28/0x50
2 locks held by nfsd/1734:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by nfsd/1735:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by nfsd/1736:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by nfsd/1737:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by nfsd/1738:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by nfsd/1739:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by nfsd/1740:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
2 locks held by nfsd/1741:
#0: (hash_sem){.+.+.+}, at: [<c1131a2d>] exp_readlock+0xd/0x10
#1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c1110f28>]
reiserfs_write_lock+0x28/0x40
next prev parent reply other threads:[~2010-02-05 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 19:03 reiserfs deadlock Alexander Beregalov
2010-02-03 19:08 ` Alexander Beregalov
2010-02-03 20:29 ` Frederic Weisbecker
2010-02-03 22:43 ` Alexander Beregalov
2010-02-03 22:52 ` Frederic Weisbecker
2010-02-05 1:46 ` Alexander Beregalov [this message]
2010-02-05 3:59 ` Frederic Weisbecker
2010-02-05 9:37 ` Alexander Beregalov
2010-02-06 10:29 ` Frederic Weisbecker
2010-02-11 18:35 ` [PATCH] reiserfs: Fix softlockup while waiting on an inode Frederic Weisbecker
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=a4423d671002041746q1d918972i7c180d38a7c1d52@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=fweisbec@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).