From: Jamie Lokier <jamie@shareable.org>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicolas Pitre <nico@marvell.com>,
Saeed Bishara <saeed@marvell.com>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182)
Date: Wed, 12 May 2010 23:21:54 +0100 [thread overview]
Message-ID: <20100512222154.GA6841@shareable.org> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C545537F@dbde02.ent.ti.com>
Shilimkar, Santosh wrote:
> There was a memory write barrier missing before the DMA descriptors
> are handed over to DMA controller.
On that note, are the cache flush functions implicit memory barriers?
-- Jamie
WARNING: multiple messages have this Message-ID (diff)
From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182)
Date: Wed, 12 May 2010 23:21:54 +0100 [thread overview]
Message-ID: <20100512222154.GA6841@shareable.org> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C545537F@dbde02.ent.ti.com>
Shilimkar, Santosh wrote:
> There was a memory write barrier missing before the DMA descriptors
> are handed over to DMA controller.
On that note, are the cache flush functions implicit memory barriers?
-- Jamie
next prev parent reply other threads:[~2010-05-12 22:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 9:23 Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182) Benjamin Herrenschmidt
2010-05-11 9:23 ` Benjamin Herrenschmidt
2010-05-11 10:16 ` Jamie Lokier
2010-05-11 10:16 ` Jamie Lokier
2010-05-11 10:47 ` Benjamin Herrenschmidt
2010-05-11 10:47 ` Benjamin Herrenschmidt
2010-05-11 10:47 ` Benjamin Herrenschmidt
2010-05-11 10:57 ` Benjamin Herrenschmidt
2010-05-11 10:57 ` Benjamin Herrenschmidt
2010-05-11 11:14 ` Shilimkar, Santosh
2010-05-11 11:14 ` Shilimkar, Santosh
2010-05-12 22:21 ` Jamie Lokier [this message]
2010-05-12 22:21 ` Jamie Lokier
2010-05-12 22:47 ` Benjamin Herrenschmidt
2010-05-12 22:47 ` Benjamin Herrenschmidt
2010-05-12 22:47 ` Benjamin Herrenschmidt
2010-05-12 23:08 ` Russell King - ARM Linux
2010-05-12 23:08 ` Russell King - ARM Linux
2010-05-14 17:41 ` Jamie Lokier
2010-05-14 17:41 ` Jamie Lokier
2010-05-14 17:59 ` Russell King - ARM Linux
2010-05-14 17:59 ` Russell King - ARM Linux
2010-05-12 23:41 ` James Bottomley
2010-05-12 23:41 ` James Bottomley
2010-05-13 0:18 ` Benjamin Herrenschmidt
2010-05-13 0:18 ` Benjamin Herrenschmidt
2010-05-13 0:18 ` Benjamin Herrenschmidt
2010-05-13 15:39 ` James Bottomley
2010-05-13 15:39 ` James Bottomley
2010-05-13 23:53 ` Benjamin Herrenschmidt
2010-05-13 23:53 ` Benjamin Herrenschmidt
2010-05-13 23:53 ` Benjamin Herrenschmidt
2010-05-13 3:12 ` FUJITA Tomonori
2010-05-13 3:12 ` FUJITA Tomonori
2010-05-13 4:42 ` Benjamin Herrenschmidt
2010-05-13 4:42 ` Benjamin Herrenschmidt
2010-05-13 4:42 ` Benjamin Herrenschmidt
2010-05-12 15:00 ` Jan Kara
2010-05-12 15:00 ` Jan Kara
2010-05-12 22:13 ` Benjamin Herrenschmidt
2010-05-12 22:13 ` Benjamin Herrenschmidt
2010-05-13 0:15 ` Benjamin Herrenschmidt
2010-05-13 0:15 ` Benjamin Herrenschmidt
2010-05-13 15:12 ` Jan Kara
2010-05-13 15:12 ` Jan Kara
2010-05-13 21:33 ` Benjamin Herrenschmidt
2010-05-13 21:33 ` Benjamin Herrenschmidt
2010-05-13 23:51 ` Benjamin Herrenschmidt
2010-05-13 23:51 ` Benjamin Herrenschmidt
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=20100512222154.GA6841@shareable.org \
--to=jamie@shareable.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=jejb@parisc-linux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@marvell.com \
--cc=saeed@marvell.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 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.