From: Shaohua Li <shli@kernel.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Lior Amsalem <alior@marvell.com>,
Thomas Petazzoni <thomas@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Boris Brezillon <boris@free-electrons.com>
Subject: Re: Possible RAID6 regression with ASYNC_TX_DMA enabled in 4.1
Date: Tue, 12 May 2015 03:59:07 -0700 [thread overview]
Message-ID: <20150512105907.GA53461@kernel.org> (raw)
In-Reply-To: <20150512125546.GJ10961@lukather>
On Tue, May 12, 2015 at 02:55:46PM +0200, Maxime Ripard wrote:
> Hi Shaohua,
>
> On Sun, May 10, 2015 at 11:26:38PM -0700, Shaohua Li wrote:
> > On Thu, May 07, 2015 at 02:57:02PM +0200, Maxime Ripard wrote:
> > > Hi,
> > >
> > > I'm currently trying to add support for the PQ operations on the
> > > marvell XOR engine, in dmaengine, obviously to be able to use async_tx
> > > to offload these operations.
> > >
> > > I'm testing these patches with a RAID6 array with 4 disks.
> > >
> > > However, since the commit 59fc630b8b5f ("RAID5: batch adjacent full
> > > stripe write", every write to that array fails with the following
> > > stacktrace.
> > >
> > > http://code.bulix.org/eh8iew-88342?raw
> > >
> > > It seems to be generated by that warning here:
> > >
> > > http://lxr.free-electrons.com/source/crypto/async_tx/async_tx.c#L173
> > >
> > > And indeed, if we dump the status of depend_tx here, it's already been
> > > acked.
> > >
> > > That doesn't happen if ASYNC_TX_DMA is disabled, hence using the
> > > software version of it, instead of relying on our XOR engine. It
> > > doesn't happen on any commit prior to the one mentionned above, with
> > > the exact same changes applied. These changes are meant to be
> > > contributed, so I can definitely push them somewhere if needed.
> > >
> > > I don't really know where to look for though, the change that is
> > > causing this is probably the change in ops_run_reconstruct6, but I'm
> > > not sure that this partial revert alone would work with regard to the
> > > rest of the patch.
> >
> > I don't have a machine with dmaengine, it's likely there is error in this side.
> > Could you please make stripe_can_batch() returns false always and check if the
> > error disappear? This should narrow down if it's related to batch issue.
>
> The error indeed disappears if stripe_can_batch always returns false.
Does this fix it?
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 77dfd72..5e820fc 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -1825,7 +1825,7 @@ ops_run_reconstruct6(struct stripe_head *sh, struct raid5_percpu *percpu,
} else
init_async_submit(&submit, 0, tx, NULL, NULL,
to_addr_conv(sh, percpu, j));
- async_gen_syndrome(blocks, 0, count+2, STRIPE_SIZE, &submit);
+ tx = async_gen_syndrome(blocks, 0, count+2, STRIPE_SIZE, &submit);
if (!last_stripe) {
j++;
sh = list_first_entry(&sh->batch_list, struct stripe_head,
next prev parent reply other threads:[~2015-05-12 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 12:57 Possible RAID6 regression with ASYNC_TX_DMA enabled in 4.1 Maxime Ripard
2015-05-07 14:39 ` AW: " Markus Stockhausen
2015-05-11 9:13 ` Maxime Ripard
2015-05-11 6:26 ` Shaohua Li
2015-05-12 12:55 ` Maxime Ripard
2015-05-12 10:59 ` Shaohua Li [this message]
2015-05-13 7:46 ` Maxime Ripard
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=20150512105907.GA53461@kernel.org \
--to=shli@kernel.org \
--cc=alior@marvell.com \
--cc=boris@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=neilb@suse.de \
--cc=thomas@free-electrons.com \
/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