This is a note to let you know that I've just added the patch titled
md: Reassigned the parameters if read_seqretry returned true in func
md_is_badblock.
to the 3.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
md-reassigned-the-parameters-if-read_seqretry-returned-true-in-func-md_is_badblock.patch
and it can be found in the queue-3.6 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From ab05613a0646dcc11049692d54bae76ca9ffa910 Mon Sep 17 00:00:00 2001
From: majianpeng <[email protected]>
Date: Tue, 6 Nov 2012 17:13:44 +0800
Subject: md: Reassigned the parameters if read_seqretry returned true in func
md_is_badblock.
From: majianpeng <[email protected]>
commit ab05613a0646dcc11049692d54bae76ca9ffa910 upstream.
This bug was introduced by commit(v3.0-rc7-126-g2230dfe).
So fix is suitable for 3.0.y thru 3.6.y.
Signed-off-by: Jianpeng Ma <[email protected]>
Signed-off-by: NeilBrown <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/md/md.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -7907,9 +7907,9 @@ int md_is_badblock(struct badblocks *bb,
sector_t *first_bad, int *bad_sectors)
{
int hi;
- int lo = 0;
+ int lo;
u64 *p = bb->page;
- int rv = 0;
+ int rv;
sector_t target = s + sectors;
unsigned seq;
@@ -7924,7 +7924,8 @@ int md_is_badblock(struct badblocks *bb,
retry:
seq = read_seqbegin(&bb->lock);
-
+ lo = 0;
+ rv = 0;
hi = bb->count;
/* Binary search between lo and hi for 'target'
Patches currently in stable-queue which might be from [email protected] are
queue-3.6/md-reassigned-the-parameters-if-read_seqretry-returned-true-in-func-md_is_badblock.patch
queue-3.6/md-avoid-write-invalid-address-if-read_seqretry-returned-true.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
