From: Andi Kleen <ak@linux.intel.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: WARNING: at /home/ak/lsrc/git/linux-2.6/fs/fs-writeback.c:356
Date: Wed, 15 Jun 2011 17:05:46 -0700 [thread overview]
Message-ID: <20110616000546.GA15121@tassilo.jf.intel.com> (raw)
Just got this shortly after booting a fresh Linus kernel on a 16 thread
system. I had some patches on top, but they were completely unrelated.
------------[ cut here ]------------
WARNING: at /home/ak/lsrc/git/linux-2.6/fs/fs-writeback.c:356 writeback_single_inode+0x65/0x1b7()
Modules linked in:
Pid: 3597, comm: flush-8:0 Not tainted 3.0.0-rc3-00061-g522a899 #164
Call Trace:
[<ffffffff81039919>] warn_slowpath_common+0x85/0x9d
[<ffffffff8103994b>] warn_slowpath_null+0x1a/0x1c
[<ffffffff810ff887>] writeback_single_inode+0x65/0x1b7
[<ffffffff810ffbe5>] writeback_sb_inodes+0xba/0x134
[<ffffffff81100592>] writeback_inodes_wb+0x16f/0x181
[<ffffffff8110080f>] wb_writeback+0x26b/0x3a7
[<ffffffff81100a92>] wb_do_writeback+0x147/0x1a0
[<ffffffff81100b77>] bdi_writeback_thread+0x8c/0x20f
[<ffffffff81100aeb>] ? wb_do_writeback+0x1a0/0x1a0
[<ffffffff81100aeb>] ? wb_do_writeback+0x1a0/0x1a0
[<ffffffff81053f11>] kthread+0x82/0x8a
[<ffffffff815e78d4>] kernel_thread_helper+0x4/0x10
[<ffffffff81053e8f>] ? kthread_worker_fn+0x13a/0x13a
[<ffffffff815e78d0>] ? gs_change+0xb/0xb
---[ end trace fc0a60eb73c3e138 ]---
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next reply other threads:[~2011-06-16 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 0:05 Andi Kleen [this message]
2011-06-18 17:29 ` WARNING: at /home/ak/lsrc/git/linux-2.6/fs/fs-writeback.c:356 Wu Fengguang
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=20110616000546.GA15121@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.