From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dmaengine: at_xdmac: lock fixes
Date: Thu, 4 Jun 2015 19:49:38 +0530 [thread overview]
Message-ID: <20150604141938.GO3140@localhost> (raw)
In-Reply-To: <1433343154-5613-1-git-send-email-ludovic.desroches@atmel.com>
On Wed, Jun 03, 2015 at 04:52:26PM +0200, Ludovic Desroches wrote:
> Using _bh variant for spin locks causes this kind of warning:
> Starting logging: ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 3 at /ssd_drive/linux/kernel/softirq.c:151
> __local_bh_enable_ip+0xe8/0xf4()
> Modules linked in:
> CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.1.0-rc2+ #94
> Hardware name: Atmel SAMA5
> [<c0013c04>] (unwind_backtrace) from [<c00118a4>] (show_stack+0x10/0x14)
> [<c00118a4>] (show_stack) from [<c001bbcc>]
> (warn_slowpath_common+0x80/0xac)
> [<c001bbcc>] (warn_slowpath_common) from [<c001bc14>]
> (warn_slowpath_null+0x1c/0x24)
> [<c001bc14>] (warn_slowpath_null) from [<c001e28c>]
> (__local_bh_enable_ip+0xe8/0xf4)
> [<c001e28c>] (__local_bh_enable_ip) from [<c01fdbd0>]
> (at_xdmac_device_terminate_all+0xf4/0x100)
> [<c01fdbd0>] (at_xdmac_device_terminate_all) from [<c02221a4>]
> (atmel_complete_tx_dma+0x34/0xf4)
> [<c02221a4>] (atmel_complete_tx_dma) from [<c01fe4ac>]
> (at_xdmac_tasklet+0x14c/0x1ac)
> [<c01fe4ac>] (at_xdmac_tasklet) from [<c001de58>]
> (tasklet_action+0x68/0xb4)
> [<c001de58>] (tasklet_action) from [<c001dfdc>]
> (__do_softirq+0xfc/0x238)
> [<c001dfdc>] (__do_softirq) from [<c001e140>] (run_ksoftirqd+0x28/0x34)
> [<c001e140>] (run_ksoftirqd) from [<c0033a3c>]
> (smpboot_thread_fn+0x138/0x18c)
> [<c0033a3c>] (smpboot_thread_fn) from [<c0030e7c>] (kthread+0xdc/0xf0)
> [<c0030e7c>] (kthread) from [<c000f480>] (ret_from_fork+0x14/0x34)
> ---[ end trace b57b14a99c1d8812 ]---
>
> It comes from the fact that devices can called some code from the DMA
> controller with irq disabled. _bh variant is not intended to be used in
> this case since it can enable irqs. Switch to irqsave/irqrestore variant to
> avoid this situation.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> Cc: stable at vger.kernel.org # 4.0 and later
> ---
> drivers/dma/at_xdmac.c | 85 ++++++++++++++++++++++++++++----------------------
> 1 file changed, 48 insertions(+), 37 deletions(-)
>
> diff --git a/drivers/dma/at_xdmac.c b/drivers/dma/at_xdmac.c
> index 9b602a6..4a7e9c6 100644
> --- a/drivers/dma/at_xdmac.c
> +++ b/drivers/dma/at_xdmac.c
> @@ -421,8 +421,9 @@ static dma_cookie_t at_xdmac_tx_submit(struct dma_async_tx_descriptor *tx)
> struct at_xdmac_desc *desc = txd_to_at_desc(tx);
> struct at_xdmac_chan *atchan = to_at_xdmac_chan(tx->chan);
> dma_cookie_t cookie;
> + unsigned long irqflags;
>
> - spin_lock_bh(&atchan->lock);
> + spin_lock_irqsave(&atchan->lock, irqflags);
> cookie = dma_cookie_assign(tx);
>
> dev_vdbg(chan2dev(tx->chan), "%s: atchan 0x%p, add desc 0x%p to xfers_list\n",
> @@ -431,7 +432,7 @@ static dma_cookie_t at_xdmac_tx_submit(struct dma_async_tx_descriptor *tx)
> if (list_is_singular(&atchan->xfers_list))
> at_xdmac_start_xfer(atchan, desc);
>
> - spin_unlock_bh(&atchan->lock);
> + spin_unlock_irqrestore(&atchan->lock, irqflags);
> return cookie;
> }
>
> @@ -591,11 +592,13 @@ at_xdmac_prep_slave_sg(struct dma_chan *chan, struct scatterlist *sgl,
> unsigned int sg_len, enum dma_transfer_direction direction,
> unsigned long flags, void *context)
> {
> - struct at_xdmac_chan *atchan = to_at_xdmac_chan(chan);
> - struct at_xdmac_desc *first = NULL, *prev = NULL;
> - struct scatterlist *sg;
> - int i;
> - unsigned int xfer_size = 0;
> + struct at_xdmac_chan *atchan = to_at_xdmac_chan(chan);
> + struct at_xdmac_desc *first = NULL, *prev = NULL;
> + struct scatterlist *sg;
> + int i;
> + unsigned int xfer_size = 0;
> + unsigned long irqflags;
> + struct dma_async_tx_descriptor *ret = NULL;
This doesnt comply with stable rules, and you should not keep this in fixes
either :(
- It cannot contain any "trivial" fixes in it (spelling changes,
whitespace cleanups, etc).
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, nicolas.ferre@atmel.com,
maxime.ripard@free-electrons.com
Subject: Re: [PATCH 1/2] dmaengine: at_xdmac: lock fixes
Date: Thu, 4 Jun 2015 19:49:38 +0530 [thread overview]
Message-ID: <20150604141938.GO3140@localhost> (raw)
In-Reply-To: <1433343154-5613-1-git-send-email-ludovic.desroches@atmel.com>
On Wed, Jun 03, 2015 at 04:52:26PM +0200, Ludovic Desroches wrote:
> Using _bh variant for spin locks causes this kind of warning:
> Starting logging: ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 3 at /ssd_drive/linux/kernel/softirq.c:151
> __local_bh_enable_ip+0xe8/0xf4()
> Modules linked in:
> CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.1.0-rc2+ #94
> Hardware name: Atmel SAMA5
> [<c0013c04>] (unwind_backtrace) from [<c00118a4>] (show_stack+0x10/0x14)
> [<c00118a4>] (show_stack) from [<c001bbcc>]
> (warn_slowpath_common+0x80/0xac)
> [<c001bbcc>] (warn_slowpath_common) from [<c001bc14>]
> (warn_slowpath_null+0x1c/0x24)
> [<c001bc14>] (warn_slowpath_null) from [<c001e28c>]
> (__local_bh_enable_ip+0xe8/0xf4)
> [<c001e28c>] (__local_bh_enable_ip) from [<c01fdbd0>]
> (at_xdmac_device_terminate_all+0xf4/0x100)
> [<c01fdbd0>] (at_xdmac_device_terminate_all) from [<c02221a4>]
> (atmel_complete_tx_dma+0x34/0xf4)
> [<c02221a4>] (atmel_complete_tx_dma) from [<c01fe4ac>]
> (at_xdmac_tasklet+0x14c/0x1ac)
> [<c01fe4ac>] (at_xdmac_tasklet) from [<c001de58>]
> (tasklet_action+0x68/0xb4)
> [<c001de58>] (tasklet_action) from [<c001dfdc>]
> (__do_softirq+0xfc/0x238)
> [<c001dfdc>] (__do_softirq) from [<c001e140>] (run_ksoftirqd+0x28/0x34)
> [<c001e140>] (run_ksoftirqd) from [<c0033a3c>]
> (smpboot_thread_fn+0x138/0x18c)
> [<c0033a3c>] (smpboot_thread_fn) from [<c0030e7c>] (kthread+0xdc/0xf0)
> [<c0030e7c>] (kthread) from [<c000f480>] (ret_from_fork+0x14/0x34)
> ---[ end trace b57b14a99c1d8812 ]---
>
> It comes from the fact that devices can called some code from the DMA
> controller with irq disabled. _bh variant is not intended to be used in
> this case since it can enable irqs. Switch to irqsave/irqrestore variant to
> avoid this situation.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> Cc: stable@vger.kernel.org # 4.0 and later
> ---
> drivers/dma/at_xdmac.c | 85 ++++++++++++++++++++++++++++----------------------
> 1 file changed, 48 insertions(+), 37 deletions(-)
>
> diff --git a/drivers/dma/at_xdmac.c b/drivers/dma/at_xdmac.c
> index 9b602a6..4a7e9c6 100644
> --- a/drivers/dma/at_xdmac.c
> +++ b/drivers/dma/at_xdmac.c
> @@ -421,8 +421,9 @@ static dma_cookie_t at_xdmac_tx_submit(struct dma_async_tx_descriptor *tx)
> struct at_xdmac_desc *desc = txd_to_at_desc(tx);
> struct at_xdmac_chan *atchan = to_at_xdmac_chan(tx->chan);
> dma_cookie_t cookie;
> + unsigned long irqflags;
>
> - spin_lock_bh(&atchan->lock);
> + spin_lock_irqsave(&atchan->lock, irqflags);
> cookie = dma_cookie_assign(tx);
>
> dev_vdbg(chan2dev(tx->chan), "%s: atchan 0x%p, add desc 0x%p to xfers_list\n",
> @@ -431,7 +432,7 @@ static dma_cookie_t at_xdmac_tx_submit(struct dma_async_tx_descriptor *tx)
> if (list_is_singular(&atchan->xfers_list))
> at_xdmac_start_xfer(atchan, desc);
>
> - spin_unlock_bh(&atchan->lock);
> + spin_unlock_irqrestore(&atchan->lock, irqflags);
> return cookie;
> }
>
> @@ -591,11 +592,13 @@ at_xdmac_prep_slave_sg(struct dma_chan *chan, struct scatterlist *sgl,
> unsigned int sg_len, enum dma_transfer_direction direction,
> unsigned long flags, void *context)
> {
> - struct at_xdmac_chan *atchan = to_at_xdmac_chan(chan);
> - struct at_xdmac_desc *first = NULL, *prev = NULL;
> - struct scatterlist *sg;
> - int i;
> - unsigned int xfer_size = 0;
> + struct at_xdmac_chan *atchan = to_at_xdmac_chan(chan);
> + struct at_xdmac_desc *first = NULL, *prev = NULL;
> + struct scatterlist *sg;
> + int i;
> + unsigned int xfer_size = 0;
> + unsigned long irqflags;
> + struct dma_async_tx_descriptor *ret = NULL;
This doesnt comply with stable rules, and you should not keep this in fixes
either :(
- It cannot contain any "trivial" fixes in it (spelling changes,
whitespace cleanups, etc).
--
~Vinod
next prev parent reply other threads:[~2015-06-04 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:52 [PATCH 1/2] dmaengine: at_xdmac: lock fixes Ludovic Desroches
2015-06-03 14:52 ` Ludovic Desroches
2015-06-03 14:52 ` [PATCH 2/2] dmaengine: at_xdmac: rework slave configuration part Ludovic Desroches
2015-06-03 14:52 ` Ludovic Desroches
2015-06-04 7:43 ` Nicolas Ferre
2015-06-04 7:43 ` Nicolas Ferre
2015-06-04 7:37 ` [PATCH 1/2] dmaengine: at_xdmac: lock fixes Nicolas Ferre
2015-06-04 7:37 ` Nicolas Ferre
2015-06-04 14:19 ` Vinod Koul [this message]
2015-06-04 14:19 ` Vinod Koul
2015-06-04 15:09 ` Ludovic Desroches
2015-06-04 15:09 ` Ludovic Desroches
2015-06-04 15:52 ` Vinod Koul
2015-06-04 15:52 ` 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=20150604141938.GO3140@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.