From: Artem Bityutskiy <dedekind@infradead.org>
To: Don Mullis <don.mullis@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CONFIG_MTD_UBI_DEBUG_DISABLE_BGT=y corrupts slab?
Date: Wed, 10 Dec 2008 12:41:54 +0200 [thread overview]
Message-ID: <1228905714.13686.236.camel@sauron> (raw)
In-Reply-To: <493F6ED2.5080402@gmail.com>
On Tue, 2008-12-09 at 23:25 -0800, Don Mullis wrote:
> With CONFIG_MTD_UBI_DEBUG_DISABLE_BGT=y, I get various corruption-caused
> OOPSes after a remount:
>
> # umount /cache
> # mount -t ubifs -o ro ubi:cache /cache
Hmm, I ran integrity test on UBIFS and had this UBI config option
enabled (as well ass emulate write and erase errors options enabled)
yesterday, and it worked fine - not slab problems and UBI was able to
recover from all errors, so the integrity check test worked fine.
But that was the latest UBIFS from the ubifs-2.6.git tree.
> I'm using a 2.6.25 kernel with the 100+ UBIFS-related patches from
> kernel.org back-ported into it, so some mismatch there is possible.
We have UBI/UBIFS backport trees, could you try ubifs-v2.6.26.git
please? It has all the UBI/UBIFS patches back-ported. Or you may just
take the patches from ubifs-v2.6.26.git and apply them to your tree.
Please, glance here:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_source
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-12-10 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 7:25 CONFIG_MTD_UBI_DEBUG_DISABLE_BGT=y corrupts slab? Don Mullis
2008-12-10 10:41 ` Artem Bityutskiy [this message]
2008-12-10 18:10 ` Don Mullis
2008-12-11 6:11 ` Artem Bityutskiy
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=1228905714.13686.236.camel@sauron \
--to=dedekind@infradead.org \
--cc=don.mullis@gmail.com \
--cc=linux-mtd@lists.infradead.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.