From: Sinan Kaya <okaya@kernel.org>
To: Shunyong Yang <shunyong.yang@hxt-semitech.com>
Cc: andy.gross@linaro.org, david.brown@linaro.org, vkoul@kernel.org,
dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
Joey Zheng <yu.zheng@hxt-semitech.com>
Subject: Re: [PATCH 2/2] dmaengine: qcom_hidma: assign channel cookie correctly
Date: Sat, 8 Dec 2018 15:28:59 -0500 [thread overview]
Message-ID: <88ef21bd-4e4f-8cce-39b3-53da45740f0f@kernel.org> (raw)
In-Reply-To: <ea6c6317dabffdcfa28cdb391b50edce98ce875d.1544156508.git.shunyong.yang@hxt-semitech.com>
On 12/6/2018 11:29 PM, Shunyong Yang wrote:
> When dma_cookie_complete() is called in hidma_process_completed(),
> dma_cookie_status() will return DMA_COMPLETE in hidma_tx_status(). Then,
> hidma_txn_is_success() will be called to use channel cookie
> mchan->last_success to do additional DMA status check. Current code
> assigns mchan->last_success after dma_cookie_complete(). This causes
> a race condition of dma_cookie_status() returns DMA_COMPLETE before
> mchan->last_success is assigned correctly. The race will cause
> hidma_tx_status() return DMA_ERROR but the transaction is actually a
> success. Moreover, in async_tx case, it will cause a timeout panic
> in async_tx_quiesce().
>
> Kernel panic - not syncing: async_tx_quiesce: DMA error waiting for
> transaction
> ...
> Call trace:
> [<ffff000008089994>] dump_backtrace+0x0/0x1f4
> [<ffff000008089bac>] show_stack+0x24/0x2c
> [<ffff00000891e198>] dump_stack+0x84/0xa8
> [<ffff0000080da544>] panic+0x12c/0x29c
> [<ffff0000045d0334>] async_tx_quiesce+0xa4/0xc8 [async_tx]
> [<ffff0000045d03c8>] async_trigger_callback+0x70/0x1c0 [async_tx]
> [<ffff0000048b7d74>] raid_run_ops+0x86c/0x1540 [raid456]
> [<ffff0000048bd084>] handle_stripe+0x5e8/0x1c7c [raid456]
> [<ffff0000048be9ec>] handle_active_stripes.isra.45+0x2d4/0x550 [raid456]
> [<ffff0000048beff4>] raid5d+0x38c/0x5d0 [raid456]
> [<ffff000008736538>] md_thread+0x108/0x168
> [<ffff0000080fb1cc>] kthread+0x10c/0x138
> [<ffff000008084d34>] ret_from_fork+0x10/0x18
>
> Cc: Joey Zheng<yu.zheng@hxt-semitech.com>
> Signed-off-by: Shunyong Yang<shunyong.yang@hxt-semitech.com>
Acked-by: Sinan Kaya <okaya@kernel.org>
to both patches 1/2 and 2/2.
next prev parent reply other threads:[~2018-12-08 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 4:28 [PATCH 1/2] dmaengine: qcom_hidma: initialize tx flags in hidma_prep_dma_* Shunyong Yang
2018-12-07 4:29 ` [PATCH 2/2] dmaengine: qcom_hidma: assign channel cookie correctly Shunyong Yang
2018-12-08 20:28 ` Sinan Kaya [this message]
2018-12-14 1:03 ` Yang, Shunyong
2019-01-04 8:56 ` Yang, Shunyong
2019-01-09 1:35 ` About some mail lost and random unsubscribe issues on this dmaengine list Yang, Shunyong
2019-01-09 6:58 ` Vinod Koul
2019-01-09 7:51 ` Yang, Shunyong
2019-01-09 16:55 ` Theodore Y. Ts'o
2019-01-04 17:31 ` [PATCH 2/2] dmaengine: qcom_hidma: assign channel cookie correctly Vinod Koul
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=88ef21bd-4e4f-8cce-39b3-53da45740f0f@kernel.org \
--to=okaya@kernel.org \
--cc=andy.gross@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=david.brown@linaro.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shunyong.yang@hxt-semitech.com \
--cc=vkoul@kernel.org \
--cc=yu.zheng@hxt-semitech.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
Powered by JetHome