CONFIG_MTD_UBI_DEBUG_DISABLE_BGT=y corrupts slab?
Artem Bityutskiy
dedekind at infradead.org
Thu Dec 11 01:11:30 EST 2008
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 (Битюцкий Артём)
More information about the linux-mtd
mailing list