From: Jens Axboe <jaxboe@fusionio.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>,
Chris Mason <chris.mason@oracle.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 21:40:14 +0200 [thread overview]
Message-ID: <4C9BAD1E.2030007@fusionio.com> (raw)
In-Reply-To: <20100923123849.8975fe47.akpm@linux-foundation.org>
On 2010-09-23 21:38, 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.
>>
>> [...]
>> 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
>> Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb
>> snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hda_intel
>> iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev snd_seq
>> snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl32 btusb
>> cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi dell_laptop snd
>> pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_page_alloc
>> rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd aes_x86_64
>> aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_helper drm
>> i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan]
>> Pid: 1073, comm: find Not tainted 2.6.36-rc5+ #8
>> Call Trace:
>> [<ffffffff8104d0e4>] warn_slowpath_common+0x85/0x9d
>> [<ffffffff8104d19f>] warn_slowpath_fmt+0x46/0x48
>> [<ffffffff811308b7>] inode_to_bdi+0x62/0x6d
>> [<ffffffff81131b48>] __mark_inode_dirty+0xd0/0x177
>> [<ffffffff81127168>] touch_atime+0x107/0x12a
>> [<ffffffff81122384>] ? filldir+0x0/0xd0
>> [<ffffffff8112259b>] vfs_readdir+0x8d/0xb4
>> [<ffffffff8112270b>] sys_getdents+0x81/0xd1
>> [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b
>
> Thanks. 692ebd17c2905313fff3c504c249c6a0faad16ec had a cc:stable in
> the changelog. I'd suggest it not be merged into -stable until this
> regression is sorted out!
It was just added, I'm discussing this with Chris on irc as I type this.
But yes, lets not replace a regression with a new regression :-). So
Greg, please hold off on these for a little while.
--
Jens Axboe
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
2010-09-23 19:40 ` Jens Axboe [this message]
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=4C9BAD1E.2030007@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=cesarb@cesarb.net \
--cc=chris.mason@oracle.com \
--cc=jack@suse.cz \
--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).