From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UBI changes for 3.7-rc9
Date: Tue, 04 Dec 2012 16:17:12 +0200 [thread overview]
Message-ID: <1354630632.11583.69.camel@sauron.fi.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Hi Linus,
it is nice that you decided to postpone 3.8, because we found a couple
of bad bugs in UBI. Please, pull the fixes.
The following changes since commit 9489e9dcae718d5fde988e4a684a0f55b5f94d17:
Linux 3.7-rc7 (2012-11-25 17:59:19 -0800)
are available in the git repository at:
git://git.infradead.org/linux-ubi.git tags/upstream-3.7-rc9
for you to fetch changes up to 894aef215775b56b725e9dde856b7a8b091ddfcc:
UBI: dont call ubi_self_check_all_ff() in __wl_get_peb() (2012-12-04 16:04:31 +0200)
----------------------------------------------------------------
Fixes for 2 brown-paperbag bugs introduced this merge window by the fastmap
code:
1. The UBI background thread got stuck when a bit-flip happened because free
LEBs was not removed from the "free" tree when we started using it.
2. I/O debugging checks did not work because we called a sleeping function in
atomic context.
----------------------------------------------------------------
Richard Weinberger (2):
UBI: remove PEB from free tree in get_peb_for_wl()
UBI: dont call ubi_self_check_all_ff() in __wl_get_peb()
drivers/mtd/ubi/wl.c | 26 ++++++++++++++++----------
1 file changed, 16 insertions(+), 10 deletions(-)
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-12-04 14:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1354630632.11583.69.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome