From: Frederic Weisbecker <fweisbec@gmail.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs deadlock
Date: Fri, 5 Feb 2010 04:59:57 +0100 [thread overview]
Message-ID: <20100205035953.GB5408@nowhere> (raw)
In-Reply-To: <a4423d671002041746q1d918972i7c180d38a7c1d52@mail.gmail.com>
On Fri, Feb 05, 2010 at 04:46:38AM +0300, Alexander Beregalov wrote:
> Hi Frederic
>
> Does it help?
Nope :-S
I need the full stracktraces. Plus the fact a thread holds
the reiserfs lock doesn't help much in this regard. This
is a drawback of lockdep: "holding" a lock in such lock dump
means either: the task holds the lock _or_ the task requests the
lock and block on it.
The only way to determine if a task really holds the reiserfs
lock is to look at the stack trace and see if it blocks on
reiserfs_write_lock_*() or something else. If this is something
else, then it means it really holds it, and there are fair
chances this is exactly the stacktrace we want: the one that
raised the softlockup.
Thanks!
next prev parent reply other threads:[~2010-02-05 4:00 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
2010-02-05 3:59 ` Frederic Weisbecker [this message]
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=20100205035953.GB5408@nowhere \
--to=fweisbec@gmail.com \
--cc=a.beregalov@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