All of lore.kernel.org
 help / color / mirror / Atom feed
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: 2.6.33-rc0: reiserfs: inconsistent lock state
Date: Mon, 14 Dec 2009 12:09:24 +0100	[thread overview]
Message-ID: <20091214110921.GA5168@nowhere> (raw)
In-Reply-To: <a4423d670912111406g5967eb1fw93e49de242fbf54@mail.gmail.com>

On Sat, Dec 12, 2009 at 01:06:29AM +0300, Alexander Beregalov wrote:
> Hi Frederic
> 
> It is x86_32 UP
> 
> 
> [ INFO: inconsistent lock state ]
> 2.6.32-05594-g3ef884b #2
[...]


Thanks! I've pushed two fixes in my tree. May be could
you test them by merging it on latest upstream?

As usual, it's on:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	reiserfs/kill-bkl

Thanks!


  parent reply	other threads:[~2009-12-14 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 22:06 2.6.33-rc0: reiserfs: inconsistent lock state Alexander Beregalov
2009-12-12 20:51 ` Alexander Beregalov
2009-12-14 11:00   ` [PATCH 2/2] reiserfs: Fix reiserfs lock and journal lock inversion dependency Frederic Weisbecker
2009-12-14 10:53 ` [PATCH 1/2] reiserfs: Fix possible recursive lock Frederic Weisbecker
2009-12-14 11:09 ` Frederic Weisbecker [this message]
2009-12-14 20:11   ` 2.6.33-rc0: reiserfs: inconsistent lock state Alexander Beregalov
2009-12-16 22:35     ` [PATCH] reiserfs: Fix reiserfs lock <-> inode mutex dependency inversion Frederic Weisbecker
2009-12-16 22:41     ` 2.6.33-rc0: reiserfs: inconsistent lock state Frederic Weisbecker
2009-12-20 12:09       ` Alexander Beregalov
2009-12-28 17:17         ` Frederic Weisbecker
2009-12-29 21:36         ` [PATCH] reiserfs: Fix remaining in-reclaim-fs <-> reclaim-fs-on locking inversion 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=20091214110921.GA5168@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 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.