public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: mq: INFO: possible circular locking dependency detected
Date: Wed, 8 Aug 2012 16:50:05 +0800	[thread overview]
Message-ID: <20120808085005.GA20927@localhost> (raw)
In-Reply-To: <50212C34.8030204@gmail.com>

On Tue, Aug 07, 2012 at 04:54:44PM +0200, Sasha Levin wrote:
> On 08/06/2012 08:34 AM, Al Viro wrote:
> > On Sat, Aug 04, 2012 at 12:59:31PM +0200, Sasha Levin wrote:
> >> Hi all,
> >>
> >> While fuzzing with trinity inside a KVM tools guest, using latest -next kernel, I've stumbled on the dump below.
> >>
> >> I think this is the result of commit 765927b2 ("switch dentry_open() to struct path, make it grab references itself").
> > 
> > 	Not quite, actually - back then the order didn't matter;
> > unfortunately, I'd missed that place when porting Jan's series,
> > which made these ordered.
> > 
> > 	Anyway, see today's vfs.git#for-linus; that should be dealt with
> > there.
> > 
> 
> Yup, that did it.

It works for me, too.

Thanks,
Fengguang

      reply	other threads:[~2012-08-08  8:50 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
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 [this message]

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=20120808085005.GA20927@localhost \
    --to=fengguang.wu@intel.com \
    --cc=davej@redhat.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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