From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs error : read_znode: bad indexing node
Date: Wed, 20 Jun 2012 14:03:50 +0300 [thread overview]
Message-ID: <1340190230.13910.122.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FE19D18.1040100@parrot.com>
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
On Wed, 2012-06-20 at 11:51 +0200, Matthieu CASTET wrote:
> We may have a driver that corrupt the heap/memory.
If it is ARM and you do DMA in your driver - this may be the cause of
issues because UBIFS uses vmalloc()'ed memory and there are issues with
DMAing it. Also, various things related to cache coherency are often the
source of issues.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-20 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 13:59 ubifs error : read_znode: bad indexing node Matthieu CASTET
2012-06-18 20:45 ` Artem Bityutskiy
2012-06-20 9:51 ` Matthieu CASTET
2012-06-20 11:03 ` Artem Bityutskiy [this message]
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=1340190230.13910.122.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.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