All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: <dsterba@suse.cz>, <lakshmipathi.g@gmail.com>
Subject: [PATCH v4 04/20] btrfs-progs: raid56: Allow raid6 to recover data and p
Date: Thu, 25 May 2017 14:21:49 +0800	[thread overview]
Message-ID: <20170525062205.11660-5-quwenruo@cn.fujitsu.com> (raw)
In-Reply-To: <20170525062205.11660-1-quwenruo@cn.fujitsu.com>

Copied from kernel lib/raid6/recov.c.

Minor modifications includes:
- Rename from raid6_datap_recov_intx() to raid5_recov_datap()
- Rename parameter from faila to dest1

Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
---
 kernel-lib/raid56.c | 41 +++++++++++++++++++++++++++++++++++++++++
 kernel-lib/raid56.h |  2 ++
 2 files changed, 43 insertions(+)

diff --git a/kernel-lib/raid56.c b/kernel-lib/raid56.c
index dca8f8d4..e078972b 100644
--- a/kernel-lib/raid56.c
+++ b/kernel-lib/raid56.c
@@ -239,3 +239,44 @@ int raid6_recov_data2(int nr_devs, size_t stripe_len, int dest1, int dest2,
 	free(zero_mem2);
 	return ret;
 }
+
+/*
+ * Raid 6 recover code copied from kernel lib/raid6/recov.c
+ * - rename from raid6_datap_recov_intx1()
+ * - parameter changed from faila to dest1
+ */
+int raid6_recov_datap(int nr_devs, size_t stripe_len, int dest1, void **data)
+{
+	u8 *p, *q, *dq;
+	const u8 *qmul;		/* Q multiplier table */
+	char *zero_mem;
+
+	p = (u8 *)data[nr_devs - 2];
+	q = (u8 *)data[nr_devs - 1];
+
+	zero_mem = calloc(1, stripe_len);
+	if (!zero_mem)
+		return -ENOMEM;
+
+	/* Compute syndrome with zero for the missing data page
+	   Use the dead data page as temporary storage for delta q */
+	dq = (u8 *)data[dest1];
+	data[dest1] = (void *)zero_mem;
+	data[nr_devs - 1] = dq;
+
+	raid6_gen_syndrome(nr_devs, stripe_len, data);
+
+	/* Restore pointer table */
+	data[dest1]   = dq;
+	data[nr_devs - 1] = q;
+
+	/* Now, pick the proper data tables */
+	qmul  = raid6_gfmul[raid6_gfinv[raid6_gfexp[dest1]]];
+
+	/* Now do it... */
+	while ( stripe_len-- ) {
+		*p++ ^= *dq = qmul[*q ^ *dq];
+		q++; dq++;
+	}
+	return 0;
+}
diff --git a/kernel-lib/raid56.h b/kernel-lib/raid56.h
index 8d64256f..83ac39a1 100644
--- a/kernel-lib/raid56.h
+++ b/kernel-lib/raid56.h
@@ -42,4 +42,6 @@ extern const u8 raid6_gfexi[256]      __attribute__((aligned(256)));
 /* Recover raid6 with 2 data corrupted */
 int raid6_recov_data2(int nr_devs, size_t stripe_len, int dest1, int dest2,
 		      void **data);
+/* Recover data and P */
+int raid6_recov_datap(int nr_devs, size_t stripe_len, int dest1, void **data);
 #endif
-- 
2.13.0




  parent reply	other threads:[~2017-05-25  6:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  6:21 [PATCH v4 00/20] Btrfs-progs offline scrub Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 01/20] btrfs-progs: raid56: Introduce raid56 header for later recovery usage Qu Wenruo
2017-05-31 13:25   ` David Sterba
2017-05-25  6:21 ` [PATCH v4 02/20] btrfs-progs: raid56: Introduce tables for RAID6 recovery Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 03/20] btrfs-progs: raid56: Allow raid6 to recover 2 data stripes Qu Wenruo
2017-05-25  6:21 ` Qu Wenruo [this message]
2017-05-25  6:21 ` [PATCH v4 05/20] btrfs-progs: Introduce wrapper to recover raid56 data Qu Wenruo
2017-05-31 13:52   ` David Sterba
2017-06-01  1:04     ` Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 06/20] btrfs-progs: Introduce new btrfs_map_block function which returns more unified result Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 07/20] btrfs-progs: Allow __btrfs_map_block_v2 to remove unrelated stripes Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 08/20] btrfs-progs: csum: Introduce function to read out data csums Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 09/20] btrfs-progs: scrub: Introduce structures to support offline scrub for RAID56 Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 10/20] btrfs-progs: scrub: Introduce functions to scrub mirror based tree block Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 11/20] btrfs-progs: scrub: Introduce functions to scrub mirror based data blocks Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 12/20] btrfs-progs: scrub: Introduce function to scrub one mirror-based extent Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 13/20] btrfs-progs: scrub: Introduce function to scrub one data stripe Qu Wenruo
2017-05-25  6:21 ` [PATCH v4 14/20] btrfs-progs: scrub: Introduce function to verify parities Qu Wenruo
2017-05-25  6:22 ` [PATCH v4 15/20] btrfs-progs: extent-tree: Introduce function to check if there is any extent in given range Qu Wenruo
2017-05-25  6:22 ` [PATCH v4 16/20] btrfs-progs: scrub: Introduce function to recover data parity Qu Wenruo
2017-05-25  6:22 ` [PATCH v4 17/20] btrfs-progs: scrub: Introduce helper to write a full stripe Qu Wenruo
2017-05-25  6:22 ` [PATCH v4 18/20] btrfs-progs: scrub: Introduce a function to scrub one " Qu Wenruo
2017-05-25  6:22 ` [PATCH v4 19/20] btrfs-progs: scrub: Introduce function to check a whole block group Qu Wenruo
2017-05-25  6:22 ` [PATCH v4 20/20] btrfs-progs: scrub: Introduce offline scrub function Qu Wenruo
2017-05-26 18:37 ` [PATCH v4 00/20] Btrfs-progs offline scrub Goffredo Baroncelli
2017-05-29  0:21   ` Qu Wenruo
2017-05-29 16:52     ` Goffredo Baroncelli
2017-05-30 18:54 ` David Sterba
2017-05-31 14:07   ` David Sterba
2017-06-18  6:20 ` Lakshmipathi.G

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=20170525062205.11660-5-quwenruo@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=dsterba@suse.cz \
    --cc=lakshmipathi.g@gmail.com \
    --cc=linux-btrfs@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.