From: Christoph Hellwig <hch@lst.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: brking@us.ibm.com, Christoph Hellwig <hch@lst.de>,
Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-block@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: ipr crashes due to NULL dma_need_drain since cc97923a5bcc ("block: move dma drain handling to scsi")
Date: Tue, 9 Jun 2020 14:04:37 +0200 [thread overview]
Message-ID: <20200609120437.GB2140@lst.de> (raw)
In-Reply-To: <87zh9cftj0.fsf@mpe.ellerman.id.au>
On Tue, Jun 09, 2020 at 08:00:35PM +1000, Michael Ellerman wrote:
> Hi all,
>
> I'm seeing crashes on powerpc with the ipr driver, which I'm fairly sure
> are due to dma_need_drain being NULL.
Ooops, my changes completely forgot about SAS attached ATAPI devices.
I'll cook up a fix in a bit.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
brking@us.ibm.com, linuxppc-dev@lists.ozlabs.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: ipr crashes due to NULL dma_need_drain since cc97923a5bcc ("block: move dma drain handling to scsi")
Date: Tue, 9 Jun 2020 14:04:37 +0200 [thread overview]
Message-ID: <20200609120437.GB2140@lst.de> (raw)
In-Reply-To: <87zh9cftj0.fsf@mpe.ellerman.id.au>
On Tue, Jun 09, 2020 at 08:00:35PM +1000, Michael Ellerman wrote:
> Hi all,
>
> I'm seeing crashes on powerpc with the ipr driver, which I'm fairly sure
> are due to dma_need_drain being NULL.
Ooops, my changes completely forgot about SAS attached ATAPI devices.
I'll cook up a fix in a bit.
next prev parent reply other threads:[~2020-06-09 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 10:00 ipr crashes due to NULL dma_need_drain since cc97923a5bcc ("block: move dma drain handling to scsi") Michael Ellerman
2020-06-09 12:04 ` Christoph Hellwig [this message]
2020-06-09 12:04 ` Christoph Hellwig
2020-06-09 15:42 ` Christoph Hellwig
2020-06-09 15:42 ` Christoph Hellwig
2020-06-10 5:43 ` Michael Ellerman
2020-06-10 5:43 ` Michael Ellerman
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=20200609120437.GB2140@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=brking@us.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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.