From: Greg KH <greg@kroah.com>
To: Martin Kepplinger <martin.kepplinger@ginzinger.com>
Cc: stable@vger.kernel.org, dedekind1@gmail.com, richard@nod.at,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ubi: fastmap: Check each mapping only once
Date: Thu, 29 Nov 2018 09:09:23 +0100 [thread overview]
Message-ID: <20181129080923.GE13859@kroah.com> (raw)
In-Reply-To: <20181126103842.3249-1-martin.kepplinger@ginzinger.com>
On Mon, Nov 26, 2018 at 11:38:42AM +0100, Martin Kepplinger wrote:
> From: Richard Weinberger <richard@nod.at>
>
> [ Upstream commit 34653fd8c46e771585fce5975e4243f8fd401914 ]
>
> This commit got merged along with commit 781932375ffc
> ("ubi: fastmap: Correctly handle interrupted erasures in EBA") upstream but
> only the latter has been applied to stable v4.14.54 as commit a23cf10d9abb.
> This resulted in a performance regression. Startup on i.MX platforms is
> delayed for up to a few seconds depending on the platform.
> This fixes ubi fastmap to be of the same performance as it has been before
> said fastmap changes.
>
> Fixes: a23cf10d9abb ("ubi: fastmap: Correctly handle interrupted erasures in EBA")
> Signed-off-by: Richard Weinberger <richard@nod.at>
> Signed-off-by: Martin Kepplinger <martin.kepplinger@ginzinger.com>
> ---
>
> Richard, although this fixes a major slowdown regression in -stable, do you
> consider this "stable" too?
>
> This applies and is tested only for the 4.14 stable tree. It seems to be
> equally relevant for 4.9 and 4.4 though.
Now queued up for 4.14.y, thanks.
greg k-h
next prev parent reply other threads:[~2018-11-29 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 10:38 [PATCH] ubi: fastmap: Check each mapping only once Martin Kepplinger
2018-11-29 8:09 ` Greg KH [this message]
2018-12-02 8:51 ` Richard Weinberger
2018-12-02 11:50 ` Sudip Mukherjee
2018-12-02 14:35 ` Sasha Levin
2018-12-02 15:02 ` Richard Weinberger
2018-12-02 15:32 ` Sasha Levin
2018-12-04 7:39 ` Martin Kepplinger
2018-12-04 7:41 ` Greg Kroah-Hartman
2018-12-02 15:04 ` Sudip Mukherjee
2018-12-06 11:09 ` Greg KH
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=20181129080923.GE13859@kroah.com \
--to=greg@kroah.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.kepplinger@ginzinger.com \
--cc=richard@nod.at \
--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 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).