From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: [2.6.34-rc5] bad page state copying to/from HFS+ filesystem...
Date: Sun, 25 Apr 2010 22:14:16 +0100 [thread overview]
Message-ID: <v2k6278d2221004251414kbbcc41baw78b86120d81dce7d@mail.gmail.com> (raw)
When copying data from a HFS+ filesystem to a freshly-created one, I
experienced page state corruption [1]. I don't have access to the
filesystem anymore, but can run some other filesystem tests if anyone
is interested.
Kernel is mainline 2.6.34-rc5 on x86-64.
Thanks,
Daniel
--- [1]
hfs: backup: 0,1953523120,244190389,3072
hfs: backup: 0,1953523120,244190389,3072
hfs: backup: 0,1953523120,244190389,3072
hfs: backup: 0,1953523120,244190389,3072
hfs: backup: 0,1953523120,244190389,3072
BUG: Bad page state in process cp pfn:37654
page:ffffea0000c1e260 count:0 mapcount:0 mapping:(null) index:0x0
page flags: 0x100000000000004(referenced)
Pid: 3163, comm: cp Not tainted 2.6.34-020634rc5-generic #020634rc5
Call Trace:
[<ffffffff810f6654>] ? dump_page+0x44/0x60
[<ffffffff810f66ff>] bad_page+0x8f/0x110
[<ffffffff8113a074>] ? try_get_mem_cgroup_from_mm+0x24/0x80
[<ffffffff810f68b3>] prep_new_page+0x133/0x150
[<ffffffff810f81a5>] get_page_from_freelist+0x1d5/0x460
[<ffffffff810f8a4a>] __alloc_pages_nodemask+0xda/0x180
[<ffffffff81127a9c>] alloc_pages_current+0x8c/0xd0
[<ffffffff810f12bd>] __page_cache_alloc+0x6d/0x80
[<ffffffff810f2edc>] grab_cache_page_write_begin+0x7c/0xc0
[<ffffffff8116a61c>] block_write_begin+0x8c/0xf0
[<ffffffff8116b89c>] cont_write_begin+0x8c/0xd0
[<ffffffffa0398110>] ? hfsplus_get_block+0x0/0x1a0 [hfsplus]
[<ffffffffa03964f6>] hfsplus_write_begin+0x36/0x40 [hfsplus]
[<ffffffffa0398110>] ? hfsplus_get_block+0x0/0x1a0 [hfsplus]
[<ffffffff810f2191>] generic_perform_write+0xc1/0x1a0
[<ffffffff810f22d5>] generic_file_buffered_write+0x65/0xa0
[<ffffffff810f3441>] __generic_file_aio_write+0x251/0x3f0
[<ffffffff810f2ce9>] ? generic_file_aio_read+0xb9/0x1b0
[<ffffffff810f363c>] generic_file_aio_write+0x5c/0xb0
[<ffffffff81140a65>] do_sync_write+0xd5/0x120
[<ffffffff81248aa6>] ? security_file_permission+0x16/0x20
[<ffffffff81141c3c>] vfs_write+0xcc/0x1a0
[<ffffffff81141e05>] sys_write+0x55/0x90
[<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
Disabling lock debugging due to kernel taint
--
Daniel J Blueman
reply other threads:[~2010-04-25 21:14 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=v2k6278d2221004251414kbbcc41baw78b86120d81dce7d@mail.gmail.com \
--to=daniel.blueman@gmail.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 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).