From: "Dan Williams" <dan.j.williams@intel.com>
To: Laurent CORBES <laurent.corbes@smartjog.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Shannon Nelson <shannon.nelson@intel.com>,
maciej.sosnowski@intel.com
Subject: Re: [BUG] OOPS 2.6.24.2 raid5 write with ioatdma
Date: Fri, 15 Feb 2008 12:17:43 -0700 [thread overview]
Message-ID: <e9c3a7c20802151117i4e8a3f1bq7be1e94433702fbf@mail.gmail.com> (raw)
In-Reply-To: <20080215171905.2e5c6bee@smartjog.com>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
On Fri, Feb 15, 2008 at 9:19 AM, Laurent CORBES
<laurent.corbes@smartjog.com> wrote:
> Hi all,
>
> I got a raid5 oops when trying to write on a raid 5 array, with ioatdma loaded
> and without DCA activated in bios:
>
At first glance I believe the attached patch may fix the issue, I'll
try to reproduce this locally.
Regards,
Dan
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: ioat-init-ack.patch --]
[-- Type: text/x-patch; name=ioat-init-ack.patch, Size: 861 bytes --]
ioat: fix 'ack' handling, driver must ensure that 'ack' is zero
From: Dan Williams <dan.j.williams@intel.com>
Initialize 'ack' to zero in case the descriptor has been recycled.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
---
drivers/dma/ioat_dma.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/dma/ioat_dma.c b/drivers/dma/ioat_dma.c
index 45e7b46..8cf542b 100644
--- a/drivers/dma/ioat_dma.c
+++ b/drivers/dma/ioat_dma.c
@@ -726,6 +726,7 @@ static struct dma_async_tx_descriptor *ioat1_dma_prep_memcpy(
if (new) {
new->len = len;
+ new->async_tx.ack = 0;
return &new->async_tx;
} else
return NULL;
@@ -749,6 +750,7 @@ static struct dma_async_tx_descriptor *ioat2_dma_prep_memcpy(
if (new) {
new->len = len;
+ new->async_tx.ack = 0;
return &new->async_tx;
} else
return NULL;
next prev parent reply other threads:[~2008-02-15 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 16:19 [BUG] OOPS 2.6.24.2 raid5 write with ioatdma Laurent CORBES
2008-02-15 19:17 ` Dan Williams [this message]
2008-02-15 19:43 ` Shannon Nelson
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=e9c3a7c20802151117i4e8a3f1bq7be1e94433702fbf@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=laurent.corbes@smartjog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=shannon.nelson@intel.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