From: Richard Weinberger <richard@nod.at>
To: Greg KH <greg@kroah.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
jean-philippe francois <jp.francois@cynove.com>,
stable@vger.kernel.org, Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Ubi patch proposition for 3.10.y
Date: Thu, 04 Sep 2014 00:08:11 +0200 [thread overview]
Message-ID: <5407914B.302@nod.at> (raw)
In-Reply-To: <20140901220258.GA28791@kroah.com>
Am 02.09.2014 00:02, schrieb Greg KH:
> On Mon, Sep 01, 2014 at 11:51:11PM +0200, Richard Weinberger wrote:
>> Am 29.08.2014 14:26, schrieb jean-philippe francois:
>>> I think commit 4b3e0a25... [1] (UBI: Call scan_all() with correct
>>> offset in error case) should be added to 3.10.y stable branch.
>>>
>>> It solves an ubifs corruption problem on my board. Edited bootlog for
>>> each case are attached.
>>>
>>> ubifs corruption can be easily reproduced on this board :
>>> 1) format nand partition and flash rootfs
>>> 2) record h264 stream on nand
>>> 3) scp a file from host pc to rootfs while 2 is ongoing
>>> 4) unplug power
>>
>> Hmm, I think this is a good point to bite the bullet and backport all
>> UBI fastmap related fixes to -stable.
Actually I meant, I need to sit down and go through the changelog and locate
them all. :)
> And what exactly would those commits be?
There you go:
e8c235b UBI: init_volumes: Ignore volumes with no LEBs
44305eb UBI: fastmap: do not miss bit-flips
604b592 UBI: fix rb_tree node comparison in add_map
5547fec UBI: fix some use after free bugs
fe24c6e UBI: Fix memory leak in ubi_attach_fastmap() error path
c22301a UBI: fastmap: fix backward compatibility with image_seq
4b3e0a2 UBI: Call scan_all() with correct offset in error case
f240dca UBI: Fix error path in scan_pool()
fb10e4d UBI: fix refill_wl_user_pool()
8930fa5 UBI: Fix invalidate_fastmap()
Thanks,
//richard
next prev parent reply other threads:[~2014-09-03 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 12:26 Ubi patch proposition for 3.10.y jean-philippe francois
2014-09-01 21:51 ` Richard Weinberger
2014-09-01 22:02 ` Greg KH
2014-09-03 22:08 ` Richard Weinberger [this message]
2014-09-08 9:47 ` Artem Bityutskiy
2014-09-08 9:51 ` Richard Weinberger
2014-09-08 9:58 ` Artem Bityutskiy
2014-09-08 10:04 ` Willy Tarreau
2014-09-08 10:13 ` Richard Genoud
2014-09-08 10:13 ` Artem Bityutskiy
2014-09-08 10:53 ` Willy Tarreau
2014-09-08 11:03 ` jean-philippe francois
2014-09-08 10:16 ` Richard Weinberger
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=5407914B.302@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=greg@kroah.com \
--cc=jp.francois@cynove.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stable@vger.kernel.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.