From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: UBIFS: assert failed in ubifs_tnc_next_ent
Date: Thu, 24 Oct 2013 14:31:04 -0300 [thread overview]
Message-ID: <20131024173103.GA2500@localhost> (raw)
In-Reply-To: <20131024164144.GC23337@ld-irv-0074.broadcom.com>
On Thu, Oct 24, 2013 at 09:41:44AM -0700, Brian Norris wrote:
> On Wed, Oct 23, 2013 at 06:31:50PM -0700, Brian Norris wrote:
> > I'll retry on 3.12-rc and with a few extra backported
> > fixes on 3.8.
>
> It looks like I was just missing a few upstream bugfixes. That's what I
> get for not properly following -stable properly :(
>
> With the additional backporting of these two commits, my filesystem
> tests survived overnight:
>
> commit 2928f0d0c5ebd6c9605c0d98207a44376387c298
> Author: Adam Thomas <adamthomas1111@gmail.com>
> Date: Sat Feb 2 22:32:31 2013 +0000
>
> UBIFS: fix use of freed ubifs_orphan objects
>
> commit 8afd500cb52a5d00bab4525dd5a560d199f979b9
> Author: Adam Thomas <adamthomas1111@gmail.com>
> Date: Sat Feb 2 22:35:08 2013 +0000
>
> UBIFS: fix double free of ubifs_orphan objects
>
> Sorry for the noise. I guess this is a lesson for others, though. Greg
> KH isn't joking when he says "all users must upgrade"!
>
Interesting findings and interesting lesson :-)
I'll keep this in mind and thanks for sharing your findings!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
prev parent reply other threads:[~2013-10-24 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 22:09 UBIFS: assert failed in ubifs_tnc_next_ent Brian Norris
2013-10-24 1:31 ` Brian Norris
2013-10-24 16:41 ` Brian Norris
2013-10-24 17:31 ` Ezequiel Garcia [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=20131024173103.GA2500@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).