From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"V, Hemanth" <hemanthv@ti.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"pierre@ossman.eu" <pierre@ossman.eu>,
saeed bishara <saeed.bishara@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Highmem issues with MMC filesystem
Date: Thu, 18 Mar 2010 17:51:21 +0000 [thread overview]
Message-ID: <20100318175120.GA7081@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1003181205020.31128@xanadu.home>
On Thu, Mar 18, 2010 at 12:17:50PM -0400, Nicolas Pitre wrote:
> On Thu, 18 Mar 2010, Russell King - ARM Linux wrote:
> > What exactly is the problem that we're discussing? Is it that the data
> > on the block device is becoming corrupted, or is the data being read off
> > the block device corrupted?
>
> Data read from a DMA based block device is corrupted in memory and
> causing all sorts of misbehavior such as segmentation faults in user
> space, or EXT2 complaining about broken filesystem metadata.
Isn't ext2 metadata read into lowmem pages?
The ext2 bitmap code sources its backing store from the old fs buffercache
code, which can only use lowmem - so the ext2 bitmaps are in lowmem (see
set_bh_page). The superblock comes from the buffercache (grep for sb_bread)
as well, so that's lowmem, and it looks to me like inode reading also
comes via the buffercache.
It seems that all ext2 metadata is in lowmem, so I don't get the highmem
interaction causing ext2 fs metadata corruption.
next prev parent reply other threads:[~2010-03-18 17:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 13:40 Highmem issues with MMC filesystem Hemanth V
2010-03-17 13:49 ` Nicolas Pitre
2010-03-17 14:40 ` Hemanth V
2010-03-17 14:58 ` Nicolas Pitre
2010-03-18 9:23 ` Russell King - ARM Linux
2010-03-18 11:15 ` saeed bishara
2010-03-18 11:24 ` Russell King - ARM Linux
2010-03-18 13:20 ` Nicolas Pitre
2010-03-18 13:30 ` Shilimkar, Santosh
2010-03-18 14:19 ` Russell King - ARM Linux
2010-03-18 14:41 ` Hemanth V
2010-03-18 16:17 ` Nicolas Pitre
2010-03-18 17:51 ` Russell King - ARM Linux [this message]
2010-03-18 19:24 ` Nicolas Pitre
2010-03-19 1:55 ` Jamie Lokier
2010-03-19 13:17 ` Nicolas Pitre
2010-03-19 13:27 ` Russell King - ARM Linux
2010-03-19 17:59 ` Nicolas Pitre
2010-03-19 18:26 ` Catalin Marinas
2010-03-19 18:56 ` Nicolas Pitre
2010-03-19 14:28 ` Hemanth V
2010-03-19 14:36 ` Shilimkar, Santosh
2010-03-19 14:45 ` Russell King - ARM Linux
2010-03-19 14:41 ` Catalin Marinas
2010-03-19 14:46 ` Russell King - ARM Linux
2010-03-19 14:52 ` Catalin Marinas
2010-03-19 14:54 ` Russell King - ARM Linux
2010-03-19 16:46 ` Catalin Marinas
2010-03-19 16:52 ` Russell King - ARM Linux
2010-03-19 17:47 ` Nicolas Pitre
2010-03-19 18:27 ` Nicolas Pitre
2010-03-19 18:38 ` Russell King - ARM Linux
2010-03-19 18:51 ` Nicolas Pitre
2010-03-22 11:45 ` Russell King - ARM Linux
2010-03-22 12:36 ` Nicolas Pitre
2010-03-19 20:14 ` Nicolas Pitre
2010-03-22 9:05 ` Hemanth V
2010-03-22 12:50 ` Nicolas Pitre
2010-03-18 13:42 ` saeed bishara
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=20100318175120.GA7081@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=hemanthv@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pierre@ossman.eu \
--cc=saeed.bishara@gmail.com \
--cc=santosh.shilimkar@ti.com \
/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).