From: Christoph Hellwig <hch@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: xfs@oss.sgi.com, lkml <linux-kernel@vger.kernel.org>,
Carsten Aulbert <carsten.aulbert@aei.mpg.de>,
Alex Elder <aelder@sgi.com>
Subject: Re: Circular locking dependency warning involing xfs on 2.6.27
Date: Thu, 21 Jan 2010 03:56:55 -0500 [thread overview]
Message-ID: <20100121085655.GA687@infradead.org> (raw)
In-Reply-To: <4B57ADB4.70002@kernel.org>
On Thu, Jan 21, 2010 at 10:28:20AM +0900, Tejun Heo wrote:
> Hello,
>
> This is on a pretty old kernel but Carsten reports that it happens
> occassionally in a pretty large setup involving 1500+ machines (please
> feel free to fill in). This happens pretty sporadically so reporting
> it just in case this is a yet unknown problem. As I understand it,
> testing with newer kernel isn't out of question but it being a
> production environment, not a very easy thing.
I think the one below is gone. We still have a very similar one that
can only happen during unmount, and we're trying to sort that one at the
VFS level (see the current thread on -fsdevel)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Alex Elder <aelder@sgi.com>,
xfs@oss.sgi.com, Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Subject: Re: Circular locking dependency warning involing xfs on 2.6.27
Date: Thu, 21 Jan 2010 03:56:55 -0500 [thread overview]
Message-ID: <20100121085655.GA687@infradead.org> (raw)
In-Reply-To: <4B57ADB4.70002@kernel.org>
On Thu, Jan 21, 2010 at 10:28:20AM +0900, Tejun Heo wrote:
> Hello,
>
> This is on a pretty old kernel but Carsten reports that it happens
> occassionally in a pretty large setup involving 1500+ machines (please
> feel free to fill in). This happens pretty sporadically so reporting
> it just in case this is a yet unknown problem. As I understand it,
> testing with newer kernel isn't out of question but it being a
> production environment, not a very easy thing.
I think the one below is gone. We still have a very similar one that
can only happen during unmount, and we're trying to sort that one at the
VFS level (see the current thread on -fsdevel)
next prev parent reply other threads:[~2010-01-21 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 1:28 Circular locking dependency warning involing xfs on 2.6.27 Tejun Heo
2010-01-21 1:28 ` Tejun Heo
2010-01-21 8:56 ` Christoph Hellwig [this message]
2010-01-21 8:56 ` Christoph Hellwig
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=20100121085655.GA687@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--cc=carsten.aulbert@aei.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=xfs@oss.sgi.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.