From: Artem Bityutskiy <dedekind1@gmail.com>
To: reiserfs-devel@vger.kernel.org
Cc: Linux FS Maling List <linux-fsdevel@vger.kernel.org>
Subject: Re: reiserfs lockdep complaint
Date: Wed, 30 May 2012 16:22:09 +0300 [thread overview]
Message-ID: <1338384129.2536.71.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1338380307.2536.70.camel@sauron.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
On Wed, 2012-05-30 at 15:18 +0300, Artem Bityutskiy wrote:
> Hi,
>
> I get the following lockdep complaint when test reiserfs in the 3.4
> kernel using xfstests. Ideas?
Reiserfs subsequently deadlocks, but it does not look like this lockdep
warning is related to that deadlock, but I am not sure.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-30 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 12:18 reiserfs lockdep complaint Artem Bityutskiy
2012-05-30 13:22 ` Artem Bityutskiy [this message]
2012-05-30 16:50 ` Artem Bityutskiy
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=1338384129.2536.71.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-devel@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).