All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	Sasha Levin <levinsasha928@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	Kamal Mostafa <kamal@canonical.com>,
	"Peter M. Petrakis" <peter.petrakis@canonical.com>,
	Dann Frazier <dann.frazier@canonical.com>,
	Massimo Morana <massimo.morana@canonical.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: mq: INFO: possible circular locking dependency detected
Date: Tue, 14 Aug 2012 23:13:31 +0100	[thread overview]
Message-ID: <20120814221331.GK23464@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120814220927.GN7122@quack.suse.cz>

On Wed, Aug 15, 2012 at 12:09:27AM +0200, Jan Kara wrote:
>   OK, this is a theoretical deadlock since mqueue (virtual) filesystem cannot
> really be frozen. But we should convert the mqueue code to deal with new
> lock ordering of i_mutex and mnt_want_write() anyway to make lockdep happy
> if anything... That file somehow escaped my conversion efforts. I'll send a
> fix tomorrow.

It's fixed in commit 98d11eacde966041ac7357d99d4079db7173dd40 (in vfs.git)

  reply	other threads:[~2012-08-14 22:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04 10:59 mq: INFO: possible circular locking dependency detected Sasha Levin
2012-08-05 17:08 ` Fengguang Wu
2012-08-07  5:04   ` Fengguang Wu
2012-08-07  6:39     ` Al Viro
2012-08-08  7:17       ` Fengguang Wu
2012-08-08  7:54         ` Fengguang Wu
2012-08-14 22:09           ` Jan Kara
2012-08-14 22:13             ` Al Viro [this message]
2012-08-14 22:29               ` Jan Kara
2012-08-06  6:34 ` Al Viro
2012-08-07 14:54   ` Sasha Levin
2012-08-08  8:50     ` Fengguang Wu

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=20120814221331.GK23464@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=dann.frazier@canonical.com \
    --cc=davej@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=jack@suse.cz \
    --cc=kamal@canonical.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=massimo.morana@canonical.com \
    --cc=peter.petrakis@canonical.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 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.