From: Pavel Vasilyev <pavel@pavlinux.ru>
To: linux-kernel@vger.kernel.org
Subject: fs/fs-writeback.c to dump
Date: Sat, 25 Sep 2010 19:52:48 +0400 [thread overview]
Message-ID: <201009251952.58749.pavel@pavlinux.ru> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 2153 bytes --]
# uname -a
Linux suse64 2.6.36-rc5+ #66 SMP PREEMPT Sat Sep 25 00:47:38 MSD 2010 x86_64
x86_64 x86_64 GNU/Linux
# git pull
Already up-to-date.
#gcc -v
...
...
gcc version 4.5.1 20100916 [gcc-4_5-branch revision 164333] (SUSE Linux)
...
#dmesg
....
------------[ cut here ]------------
WARNING: at fs/fs-writeback.c:87 __mark_inode_dirty+0x131/0x260()
Hardware name: S2895
Dirtiable inode bdi default != sb bdi btrfs
Modules linked in: ipt_REJECT xt_hl xt_DSCP iptable_nat nf_nat
nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 cpufreq_ondemand zram(C) nvidia
evdev snd_intel8x0 snd_ac97_codec ac97_bus
Pid: 32127, comm: git Tainted: G M WC 2.6.36-rc5+ #66
Call Trace:
[<ffffffff81037f3b>] ? warn_slowpath_common+0x7b/0xc0
[<ffffffff81038035>] ? warn_slowpath_fmt+0x45/0x50
[<ffffffff810d79d1>] ? __mark_inode_dirty+0x131/0x260
[<ffffffff810ccc4d>] ? touch_atime+0x13d/0x190
[<ffffffff810c74af>] ? vfs_readdir+0xbf/0xd0
[<ffffffff810c768f>] ? sys_getdents64+0x7f/0xe0
[<ffffffff810022eb>] ? system_call_fastpath+0x16/0x1b
---[ end trace fec92d861b8f03b8 ]---
------------[ cut here ]------------
WARNING: at fs/fs-writeback.c:87 __mark_inode_dirty+0x131/0x260()
Hardware name: S2895
Dirtiable inode bdi default != sb bdi btrfs
Modules linked in: ipt_REJECT xt_hl xt_DSCP iptable_nat nf_nat
nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 cpufreq_ondemand zram(C) nvidia
evdev snd_intel8x0 snd_ac97_codec ac97_bus
Pid: 32207, comm: touch Tainted: G M WC 2.6.36-rc5+ #66
Call Trace:
[<ffffffff81037f3b>] ? warn_slowpath_common+0x7b/0xc0
[<ffffffff81038035>] ? warn_slowpath_fmt+0x45/0x50
[<ffffffff810d79d1>] ? __mark_inode_dirty+0x131/0x260
[<ffffffff81197ce0>] ? btrfs_setattr+0x90/0x2b0
[<ffffffff8103ca6d>] ? current_fs_time+0xd/0x50
[<ffffffff810ce66f>] ? notify_change+0x12f/0x380
[<ffffffff810dc49d>] ? utimes_common+0xcd/0x1d0
[<ffffffff810dc673>] ? do_utimes+0xd3/0xf0
[<ffffffff810dc72c>] ? sys_utimensat+0x2c/0x90
[<ffffffff810b72af>] ? do_sys_open+0xbf/0x130
[<ffffffff810022eb>] ? system_call_fastpath+0x16/0x1b
---[ end trace fec92d861b8f03b9 ]---
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2010-09-25 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201009251952.58749.pavel@pavlinux.ru \
--to=pavel@pavlinux.ru \
--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.