Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Dan Williams <djbw@fb.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	Vinod Koul <vinod.koul@intel.com>,
	Tomasz Figa <t.figa@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH] raid5: panic() on dma_wait_for_async_tx() error
Date: Mon, 19 Nov 2012 12:06:32 +1100	[thread overview]
Message-ID: <20121119120632.1c97e306@notabene.brown> (raw)
In-Reply-To: <201211081220.55281.b.zolnierkie@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]


Hi Dan,
 could you comment on this please?  Would it make sense to arrange for errors
 to propagate up?  Or should we arrange to do a software-fallback in the dma
 engine is a problem?  What sort of things can cause error here anyway?

Thanks,
NeilBrown



On Thu, 08 Nov 2012 12:20:55 +0100 Bartlomiej Zolnierkiewicz
<b.zolnierkie@samsung.com> wrote:

> On Thursday 08 November 2012 12:15:26 Alan Cox wrote:
> > On Thu, 08 Nov 2012 11:06:29 +0100
> > Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> wrote:
> > 
> > > From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > > Subject: [PATCH] raid5: panic() on dma_wait_for_async_tx() error
> > > 
> > > There is not much we can do on dma_wait_for_async_tx() error
> > > so just panic() for now.
> > > 
> > > Cc: Neil Brown <neilb@suse.de>
> > > Cc: Vinod Koul <vinod.koul@intel.com>
> > > Cc: Dan Williams <djbw@fb.com>
> > > Cc: Tomasz Figa <t.figa@samsung.com>
> > > Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > > ---
> > >  drivers/md/raid5.c |    4 +++-
> > >  1 file changed, 3 insertions(+), 1 deletion(-)
> > > 
> > > Index: b/drivers/md/raid5.c
> > > ===================================================================
> > > --- a/drivers/md/raid5.c	2012-11-07 16:25:19.480876012 +0100
> > > +++ b/drivers/md/raid5.c	2012-11-07 16:27:46.244875992 +0100
> > > @@ -3223,7 +3223,9 @@ static void handle_stripe_expansion(stru
> > >  	/* done submitting copies, wait for them to complete */
> > >  	if (tx) {
> > >  		async_tx_ack(tx);
> > > -		dma_wait_for_async_tx(tx);
> > > +		if (dma_wait_for_async_tx(tx) != DMA_SUCCESS)
> > > +			panic("%s: DMA error waiting for transaction\n",
> > > +			      __func__);
> > 
> > Thats a really horrible place to panic.
> 
> Still it seems better thing to do than silently ignoring errors
> and trying to continue operations with inconsistent data.
> 
> Unfortunately higher-layers don't support error conditions and
> fixing them seems to be non-trivial task.
> 
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung Poland R&D Center
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-11-19  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 10:06 [PATCH] raid5: panic() on dma_wait_for_async_tx() error Bartlomiej Zolnierkiewicz
2012-11-08 11:15 ` Alan Cox
2012-11-08 11:20   ` Bartlomiej Zolnierkiewicz
2012-11-19  1:06     ` NeilBrown [this message]
2012-11-19  5:22       ` Dan Williams
2012-11-19 22:18         ` NeilBrown
2012-11-20  2:23           ` Dan Williams
2012-11-20  3:13             ` NeilBrown

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=20121119120632.1c97e306@notabene.brown \
    --to=neilb@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=b.zolnierkie@samsung.com \
    --cc=djbw@fb.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=t.figa@samsung.com \
    --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