[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CA12F01.2@cesarb.net>
Date: Mon, 27 Sep 2010 20:55:45 -0300
From: Cesar Eduardo Barros <cesarb@...arb.net>
To: Jan Kara <jack@...e.cz>
CC: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Jens Axboe <jaxboe@...ionio.com>,
Chris Mason <chris.mason@...cle.com>,
linux-btrfs@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org, stable@...nel.org,
Jens Axboe <axboe@...nel.dk>,
MichaĆ Piotrowski <mkkp4x4@...il.com>,
Chuck Ebbert <cebbert@...hat.com>,
kernel@...ts.fedoraproject.org
Subject: Re: Dirtiable inode bdi default != sb bdi btrfs
Em 27-09-2010 19:25, Jan Kara escreveu:
> [Added CCs for similar ecryptfs warning]
> On Thu 23-09-10 12:38:49, Andrew Morton wrote:
>>> [...]
>>> device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transid 22342
>>> /dev/mapper/vg_cesarbinspiro-lv_home
>>> SELinux: initialized (dev dm-3, type btrfs), uses xattr
>>> ------------[ cut here ]------------
>>> WARNING: at fs/fs-writeback.c:87 inode_to_bdi+0x62/0x6d()
>>> Hardware name: Inspiron N4010
>>> Dirtiable inode bdi default != sb bdi btrfs
> That suggests that we should probably handle such cases in a more generic
> way by changing the code in inode_init_always(). The patch below makes at
> least btrfs happy for me... Could you maybe test it? Thanks.
Applied on top of v2.6.36-rc5-151-g32163f4, running it right now. The
warning messages no longer happen, and everything seems to be working fine.
Tested-by: Cesar Eduardo Barros <cesarb@...arb.net>
--
Cesar Eduardo Barros
cesarb@...arb.net
cesar.barros@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists