From: Chris Mason <chris.mason@oracle.com>
To: "Smets, Jan (Jan)" <jan.smets@alcatel-lucent.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Inode to bdi issue?
Date: Wed, 20 Oct 2010 09:59:38 -0400 [thread overview]
Message-ID: <20101020135938.GH3400@think> (raw)
In-Reply-To: <14C7F4F06DB5814AB0DE29716C4F6D670EB36236@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
On Wed, Oct 20, 2010 at 03:03:00PM +0200, Smets, Jan (Jan) wrote:
> Hi list
>
> Just a quick cut 'n paste report from my dmesg. Let me know if I can help any furter.
>
> 2.6.36~rc6
>
> PS: I think this is identical to the problem reported on 23/09 "Dirtiable inode bdi default != sb bdi btrfs", and might already be fixed in rc6+ , but there are some other traces in here, so I just want to make sure it's all covered :-)
Correct, this one is already fixed. Just do a git pull from Linus' tree
and you'll get the fix.
-chris
next prev parent reply other threads:[~2010-10-20 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 13:03 Inode to bdi issue? Smets, Jan (Jan)
2010-10-20 13:59 ` Chris Mason [this message]
2010-10-20 17:20 Tomasz Chmielewski
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=20101020135938.GH3400@think \
--to=chris.mason@oracle.com \
--cc=jan.smets@alcatel-lucent.com \
--cc=linux-btrfs@vger.kernel.org \
/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).