linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Chris Mason <mason@suse.com>
Cc: linux-fsdevel@vger.kernel.org, reiserfs-dev@namesys.com
Subject: Re: [PATCH] fix reiserfs lock inversion of bkl vs inode semaphore
Date: Fri, 4 Aug 2006 15:51:20 -0700	[thread overview]
Message-ID: <20060804155120.d33f53d1.akpm@osdl.org> (raw)
In-Reply-To: <20060804140015.GD1134@watt.suse.com>

On Fri, 4 Aug 2006 10:00:15 -0400
Chris Mason <mason@suse.com> wrote:

> The correct lock ordering is inode lock -> BKL

hm.  With CONFIG_PREEMPT_BKL=y we should be getting lockdep warnings and
deadlocks, shouldn't we?  I recall seeing reports of neither.


  reply	other threads:[~2006-08-04 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 14:00 [PATCH] fix reiserfs lock inversion of bkl vs inode semaphore Chris Mason
2006-08-04 22:51 ` Andrew Morton [this message]
2006-08-05 16:21   ` Arjan van de Ven
2006-08-04 22:56 ` Andrew Morton

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=20060804155120.d33f53d1.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiserfs-dev@namesys.com \
    /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).