From: Christoph Hellwig <hch@infradead.org>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: xfs-masters@oss.sgi.com, xfs@oss.sgi.com
Subject: Re: Inconsistent {RECLAIM_FS-ON-R} -> {IN-RECLAIM_FS-W} usage in XFS
Date: Tue, 6 Oct 2009 09:10:20 -0400 [thread overview]
Message-ID: <20091006131020.GA12343@infradead.org> (raw)
In-Reply-To: <4ACB3AC5.4010603@vlnb.net>
On Tue, Oct 06, 2009 at 04:40:37PM +0400, Vladislav Bolkhovitin wrote:
> Hello,
>
> After upgrading to 2.6.31 with SCST testings I started seeing the
> following lockdep messages. I have not seen them in 2.6.29. Looks like
> it's something recently introduced.
The lockdep code to track this has been recently introduced.
I've sent some patches to fix it ages ago, but so far no one has
bothered to review them.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-06 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 12:40 Inconsistent {RECLAIM_FS-ON-R} -> {IN-RECLAIM_FS-W} usage in XFS Vladislav Bolkhovitin
2009-10-06 13:10 ` Christoph Hellwig [this message]
2009-10-21 16:29 ` Eric Sandeen
2009-10-22 8:30 ` [xfs-masters] " 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=20091006131020.GA12343@infradead.org \
--to=hch@infradead.org \
--cc=vst@vlnb.net \
--cc=xfs-masters@oss.sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox