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: Thu, 11 Dec 2008 08:11:30 +0200 [thread overview]
Message-ID: <1228975890.13686.370.camel@sauron> (raw)
In-Reply-To: <49400626.8030408@gmail.com>
On Wed, 2008-12-10 at 10:10 -0800, Don Mullis wrote:
> Artem Bityutskiy wrote:
> > 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.
>
> Thanks for testing, that helps me narrow the search.
Note, the CONFIG_MTD_UBI_DEBUG_DISABLE_BGT is debugging option, which
was introduce to test UBI correctness, because theoretically it should
work even if the thread dies or does not exist. However, UBI becomes
less efficient without the thread, so I'd recommend to use it only for
developing/test purposes.
> > 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.
>
> I assume you meant "ubifs-v2.6.25.git" -- I'm stuck at 2.6.25 for
> the present due to some out-of-tree drivers. I'll try extracting
> patches from git://git.infradead.org/~dedekind/ubifs-v2.6.25.git
> and applying them to my tree.
Right, I meant ubifs-v2.6.25.git.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-12-11 6:13 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
2008-12-10 18:10 ` Don Mullis
2008-12-11 6:11 ` 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=1228975890.13686.370.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox