From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brent Taylor <motobud@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI leb_write_unlock NULL pointer Oops
Date: Mon, 01 Jul 2013 10:05:31 +0300 [thread overview]
Message-ID: <1372662331.22014.27.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAP+RiCCTo-_iH=bXuZMYY_BCMZjZzAkTB7Nm0_B0i2FErv+VAQ@mail.gmail.com>
On Mon, 2013-05-13 at 18:09 -0500, Brent Taylor wrote:
> I'm working with an atmel at91sam9g20 evaluation board
> (http://www.atmel.com/Images/doc6413.pdf) running the Linux kernel
> version 3.6.9. On two occasions I have had the following Oops
> reported:
Looks like some kind of memory corruption, or use after free. I do not
have other ideas.
Well, another comment I could give is that the LEB locking in UBI is
over-engineered, and could be simplified.
> I have found the ubifs-v3.6.git tree but since I'm using version
> 3.6.9, how can I easily apply all the patches from 3.6 to the current
> release since some of the patches seem to have already made it into
> the 3.6.9 release.
We discovered a bug recently which may cause memory corruptions. I do
not know if it is accountable for this problem or not, but it is worth
having it. See these patches in the l2-mtd.git tree:
605c912bb843c024b1ed173dc427cd5c08e5d54d UBIFS: fix a horrid bug
33f1a63ae84dfd9ad298cf275b8f1887043ced36 UBIFS: prepare to fix a horrid bug
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-07-01 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 23:09 UBI leb_write_unlock NULL pointer Oops Brent Taylor
2013-06-25 13:13 ` Jan Lübbe
2013-07-01 7:05 ` Artem Bityutskiy [this message]
2013-07-01 14:50 ` Brent Taylor
2013-07-09 8:23 ` enrico benetti
2013-07-09 16:08 ` enrico benetti
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=1372662331.22014.27.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=motobud@gmail.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.