linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent CARON <lcaron@unix-scripts.info>
To: Dan Williams <djbw@fb.com>
Cc: Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	Vinod Koul <vinod.koul@intel.com>
Subject: Re: Strange crash on Dell R720xd
Date: Wed, 17 Oct 2012 09:31:21 +0200	[thread overview]
Message-ID: <20121017092903.ahgeefai@trusted.unix-scripts.info> (raw)
In-Reply-To: <CAA9_cmf9XsQ7YPLfsvvjPjLxQGVde1yHqTanOjJxdjPcLRUK8g@mail.gmail.com>

On Tue, Oct 16, 2012 at 10:58:49AM -0700, Dan Williams wrote:
> I think this may be a bug in __raid_run_ops that is only possible when
> raid offload and CONFIG_MULTICORE_RAID456 are enabled.  I'm thinking
> the descriptor is completed and recycled to another requester in the
> space between these two events:
> 
>                 ops_run_compute();
> 
>                 /* terminate the chain if reconstruct is not set to be run */
>                 if (tx && !test_bit(STRIPE_OP_RECONSTRUCT, &ops_request))
>                         async_tx_ack(tx);
> 
> ...don't use the experimental CONFIG_MULTICORE_RAID456 even if you
> leave IOAT DMA disabled.  A rework of the raid operation dma chaining
> is in progress, but may not be ready for a while.

Hi,

I usually don't use CONFIG_MULTICORE_RAID456 as it proved to be sluggish
and/or unstable in my experience, so I should be pretty safe letting I/O
AT DMA disabled for now on those bosex.

Thanks

      reply	other threads:[~2012-10-17  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121015213522.kaiyahro@trusted.unix-scripts.info>
2012-10-16  9:03 ` Strange crash on Dell R720xd Borislav Petkov
2012-10-16  9:26   ` Laurent CARON
2012-10-16 12:48     ` Borislav Petkov
2012-10-16 12:52       ` Laurent CARON
2012-10-16 17:58         ` Dan Williams
2012-10-17  7:31           ` Laurent CARON [this message]

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=20121017092903.ahgeefai@trusted.unix-scripts.info \
    --to=lcaron@unix-scripts.info \
    --cc=bp@alien8.de \
    --cc=djbw@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=vinod.koul@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;
as well as URLs for NNTP newsgroup(s).