From: Ted Ts'o <tytso-3s7WtUTddSA@public.gmane.org>
To: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Cc: Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Maciej Rutecki
<maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Florian Mickler <florian-sVu6HhrpSfRAfugRpC6u6w@public.gmane.org>,
Cesar Eduardo Barros
<cesarb-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
Subject: Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
Date: Sat, 2 Oct 2010 22:27:07 -0400 [thread overview]
Message-ID: <20101003022707.GN21129@thunk.org> (raw)
In-Reply-To: <201010022358.35972.rjw-KKrjLPT3xs0@public.gmane.org>
On Sat, Oct 02, 2010 at 11:58:35PM +0200, Rafael J. Wysocki wrote:
> On Saturday, October 02, 2010, Ted Ts'o wrote:
> > On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.35. Please verify if it still should be listed and let the tracking team
> > > know (either way).
> > >
> > >
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=19062
> > > Subject : Dirtiable inode bdi default != sb bdi btrfs
> > > Submitter : Cesar Eduardo Barros <cesarb-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > > Date : 2010-09-23 0:54 (4 days old)
> > > Message-ID : <4C9AA546.6050201-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > > References : http://marc.info/?l=linux-kernel&m=128520328929595&w=2
> >
> > Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
> > when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
> > partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
> > systems. So I'm seeing this as a known regression from rc3 to rc6.
> > Maybe it's different bug with ext4, but in any case, it's highly
> > annoying.
>
> Thanks for the info. I wonder who should see this report.
Oops, correction, the correct warning that I'm seeing is:
Dirtiable inode bdi block != sb bdi block
^^^^^ ^^^^^
------------[ cut here ]------------
WARNING: at /usr/projects/linux/ext4/fs/fs-writeback.c:87 inode_to_bdi+0x4e/0x5c()
Hardware name:
Dirtiable inode bdi block != sb bdi block
Modules linked in:
Pid: 21649, comm: mkfs.ext4 Tainted: G W 2.6.36-rc6-00016-gcc25699 #735
Call Trace:
[<c015a2e2>] warn_slowpath_common+0x6a/0x7f
[<c020a762>] ? inode_to_bdi+0x4e/0x5c
[<c015a36a>] warn_slowpath_fmt+0x2b/0x2f
[<c020a762>] inode_to_bdi+0x4e/0x5c
[<c020b6c3>] __mark_inode_dirty+0xaf/0x162
[<c0202305>] file_update_time+0xcc/0xe9
[<c01c68dd>] __generic_file_aio_write+0x136/0x28f
[<c02145a4>] blkdev_aio_write+0x33/0x72
[<c01f20da>] do_sync_write+0x8f/0xca
[<c0647678>] ? mutex_unlock+0xd/0xf
[<c030d528>] ? security_file_permission+0x27/0x2b
[<c01f227c>] ? rw_verify_area+0x9d/0xc0
[<c01f204b>] ? do_sync_write+0x0/0xca
[<c01f2629>] vfs_write+0x85/0xe3
[<c01f2725>] sys_write+0x40/0x62
[<c064915d>] syscall_call+0x7/0xb
---[ end trace 1f39401760ab3a42 ]---
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Ted Ts'o" <tytso@mit.edu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Florian Mickler <florian@mickler.org>,
Cesar Eduardo Barros <cesarb@cesarb.net>,
Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
Date: Sat, 2 Oct 2010 22:27:07 -0400 [thread overview]
Message-ID: <20101003022707.GN21129@thunk.org> (raw)
In-Reply-To: <201010022358.35972.rjw@sisk.pl>
On Sat, Oct 02, 2010 at 11:58:35PM +0200, Rafael J. Wysocki wrote:
> On Saturday, October 02, 2010, Ted Ts'o wrote:
> > On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.35. Please verify if it still should be listed and let the tracking team
> > > know (either way).
> > >
> > >
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=19062
> > > Subject : Dirtiable inode bdi default != sb bdi btrfs
> > > Submitter : Cesar Eduardo Barros <cesarb@cesarb.net>
> > > Date : 2010-09-23 0:54 (4 days old)
> > > Message-ID : <4C9AA546.6050201@cesarb.net>
> > > References : http://marc.info/?l=linux-kernel&m=128520328929595&w=2
> >
> > Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
> > when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
> > partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
> > systems. So I'm seeing this as a known regression from rc3 to rc6.
> > Maybe it's different bug with ext4, but in any case, it's highly
> > annoying.
>
> Thanks for the info. I wonder who should see this report.
Oops, correction, the correct warning that I'm seeing is:
Dirtiable inode bdi block != sb bdi block
^^^^^ ^^^^^
------------[ cut here ]------------
WARNING: at /usr/projects/linux/ext4/fs/fs-writeback.c:87 inode_to_bdi+0x4e/0x5c()
Hardware name:
Dirtiable inode bdi block != sb bdi block
Modules linked in:
Pid: 21649, comm: mkfs.ext4 Tainted: G W 2.6.36-rc6-00016-gcc25699 #735
Call Trace:
[<c015a2e2>] warn_slowpath_common+0x6a/0x7f
[<c020a762>] ? inode_to_bdi+0x4e/0x5c
[<c015a36a>] warn_slowpath_fmt+0x2b/0x2f
[<c020a762>] inode_to_bdi+0x4e/0x5c
[<c020b6c3>] __mark_inode_dirty+0xaf/0x162
[<c0202305>] file_update_time+0xcc/0xe9
[<c01c68dd>] __generic_file_aio_write+0x136/0x28f
[<c02145a4>] blkdev_aio_write+0x33/0x72
[<c01f20da>] do_sync_write+0x8f/0xca
[<c0647678>] ? mutex_unlock+0xd/0xf
[<c030d528>] ? security_file_permission+0x27/0x2b
[<c01f227c>] ? rw_verify_area+0x9d/0xc0
[<c01f204b>] ? do_sync_write+0x0/0xca
[<c01f2629>] vfs_write+0x85/0xe3
[<c01f2725>] sys_write+0x40/0x62
[<c064915d>] syscall_call+0x7/0xb
---[ end trace 1f39401760ab3a42 ]---
- Ted
next prev parent reply other threads:[~2010-10-03 2:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 19:55 2.6.36-rc5-git7: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-26 19:55 ` Rafael J. Wysocki
2010-09-26 19:55 ` [Bug #16951] hackbench regression with 2.6.36-rc1 Rafael J. Wysocki
2010-09-26 19:55 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17061] 2.6.36-rc1 on zaurus: bluetooth regression Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-10-02 16:52 ` Ted Ts'o
2010-10-02 16:52 ` Ted Ts'o
[not found] ` <20101002165215.GK21129-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2010-10-03 11:21 ` Vegard Nossum
2010-10-03 11:21 ` Vegard Nossum
2010-09-26 20:04 ` [Bug #17121] Two blank rectangles more than 10 cm long when booting Rafael J. Wysocki
2010-09-27 6:01 ` Eric Valette
2010-09-27 6:01 ` Eric Valette
[not found] ` <4CA03341.3030809-GANU6spQydw@public.gmane.org>
2010-09-27 19:41 ` Rafael J. Wysocki
2010-09-27 19:41 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18962] screen failes in kde Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18342] [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17722] 2.6.36-rc3: WARNING: at net/mac80211/scan.c:269 ieee80211_scan_completed Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18742] PROBLEM: Kernel panic on 2.6.36-rc4 when loading intel_ips on Core i3 laptop Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19052] 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs Rafael J. Wysocki
2010-10-02 16:54 ` Ted Ts'o
2010-10-02 16:54 ` Ted Ts'o
[not found] ` <20101002165433.GL21129-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2010-10-02 21:58 ` Rafael J. Wysocki
2010-10-02 21:58 ` Rafael J. Wysocki
[not found] ` <201010022358.35972.rjw-KKrjLPT3xs0@public.gmane.org>
2010-10-03 2:27 ` Ted Ts'o [this message]
2010-10-03 2:27 ` Ted Ts'o
[not found] ` <20101003022707.GN21129-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2010-10-03 15:16 ` Tejun Heo
2010-10-03 15:16 ` Tejun Heo
[not found] ` <4CA89E63.4080907-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2010-10-04 9:59 ` Jan Kara
2010-10-04 9:59 ` Jan Kara
[not found] ` <20101004095943.GE3589-+0h/O2h83AeN3ZZ/Hiejyg@public.gmane.org>
2010-10-04 10:12 ` Christoph Hellwig
2010-10-04 10:12 ` Christoph Hellwig
[not found] ` <20101004101212.GA25617-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2010-10-04 17:46 ` Jens Axboe
2010-10-04 17:46 ` Jens Axboe
2010-10-04 20:09 ` Andrew Morton
2010-10-04 20:09 ` Andrew Morton
[not found] ` <20101004130911.1375c6e3.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2010-10-05 15:59 ` Ted Ts'o
2010-10-05 15:59 ` Ted Ts'o
2010-09-26 20:04 ` [Bug #18992] warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19002] Radeon rv730 AGP/KMS/DRM kernel lockup Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-27 10:28 ` Mikael Pettersson
2010-09-27 10:28 ` Mikael Pettersson
[not found] ` <19616.29125.40521.717013-tgku4HJDRZih8lFjZTKsyTAV6s6igYVG@public.gmane.org>
2010-09-27 19:43 ` Rafael J. Wysocki
2010-09-27 19:43 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19082] fs/fs-writeback.c to dump Rafael J. Wysocki
2010-09-26 23:40 ` Pavel Vasilyev
-- strict thread matches above, loose matches on Subject: below --
2010-10-03 21:15 2.6.36-rc6-git2: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-10-03 21:19 ` [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs Rafael J. Wysocki
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=20101003022707.GN21129@thunk.org \
--to=tytso-3s7wtutddsa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=cesarb-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org \
--cc=florian-sVu6HhrpSfRAfugRpC6u6w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.