From: Chris Mason <chris.mason@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Cesar Eduardo Barros <cesarb@cesarb.net>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Jens Axboe <jaxboe@fusionio.com>,
linux-btrfs@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, stable@kernel.org,
Jens Axboe <axboe@kernel.dk>
Subject: Re: Dirtiable inode bdi default != sb bdi btrfs
Date: Thu, 23 Sep 2010 15:40:01 -0400 [thread overview]
Message-ID: <20100923194001.GG25023@think> (raw)
In-Reply-To: <20100923123849.8975fe47.akpm@linux-foundation.org>
On Thu, Sep 23, 2010 at 12:38:49PM -0700, Andrew Morton wrote:
>
> (Cc stable@kernel.org)
>
> On Wed, 22 Sep 2010 21:54:30 -0300
> Cesar Eduardo Barros <cesarb@cesarb.net> wrote:
>
> > This started appearing for me on v2.6.36-rc5-49-gc79bd89; it did not
> > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does not have
> > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which introduces the
> > warning.
The problem is that btrfs isn't setting the inode bdi on the directory
inode. I'm digging now to see if this code is right for
blockdevice/special inodes as well.
-chris
next prev parent reply other threads:[~2010-09-23 19:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 0:54 Dirtiable inode bdi default != sb bdi btrfs Cesar Eduardo Barros
2010-09-23 19:38 ` Andrew Morton
2010-09-23 19:40 ` Chris Mason [this message]
2010-09-23 19:40 ` Jens Axboe
2010-09-23 20:53 ` [stable] " Greg KH
2010-09-24 18:39 ` Jens Axboe
2010-09-27 0:15 ` Greg KH
2010-09-27 22:25 ` Jan Kara
2010-09-27 22:54 ` Chris Mason
2010-09-27 23:51 ` Jan Kara
2010-09-28 7:05 ` Artem Bityutskiy
2010-09-29 13:00 ` Jan Kara
2010-09-29 13:40 ` Artem Bityutskiy
2010-09-29 8:19 ` Christoph Hellwig
[not found] ` <20100929081936.GA23322@lst.de>
[not found] ` <20100929081936.GA23322-jcswGhMUV9g@public.gmane.org>
2010-09-29 12:18 ` Jan Kara
2010-09-29 14:10 ` Christoph Hellwig
2010-09-29 23:38 ` Jan Kara
2010-09-30 0:06 ` Christoph Hellwig
2010-09-27 23:55 ` Cesar Eduardo Barros
[not found] ` <4CA12F01.2-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
2010-09-29 13:01 ` Jan Kara
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=20100923194001.GG25023@think \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=cesarb@cesarb.net \
--cc=jack@suse.cz \
--cc=jaxboe@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).