From: vitor <vitor.soares@synopsys.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Vitor Soares <vitor.soares@synopsys.com>,
Boris Brezillon <bbrezillon@kernel.org>
Cc: "linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] i3c: master: dw: fix deadlock
Date: Fri, 25 Jan 2019 11:55:50 +0000 [thread overview]
Message-ID: <54d8926f-f0fd-c2c7-1b8a-dce1384892b7@synopsys.com> (raw)
In-Reply-To: <20190125152300.248d58f4@xhacker.debian>
Hi Jisheng,
Thanks for your report.
On 25/01/19 07:29, Jisheng Zhang wrote:
> In dw_i3c_master_irq_handler(), we already have gotten
> &master->xferqueue.lock, if we try to get the same lock again in
> dw_i3c_master_dequeue_xfer(), deadlock happens.
>
> We fix this issue by introduing dw_i3c_master_dequeue_xfer_locked()
> which does all what dw_i3c_master_dequeue_xfer() does without trying
> to lock &master->xferqueue.lock.
>
> Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> ---
> drivers/i3c/master/dw-i3c-master.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/i3c/master/dw-i3c-master.c b/drivers/i3c/master/dw-i3c-master.c
> index f8c00b94817f..bb03079fbade 100644
> --- a/drivers/i3c/master/dw-i3c-master.c
> +++ b/drivers/i3c/master/dw-i3c-master.c
> @@ -419,12 +419,9 @@ static void dw_i3c_master_enqueue_xfer(struct dw_i3c_master *master,
> spin_unlock_irqrestore(&master->xferqueue.lock, flags);
> }
>
> -static void dw_i3c_master_dequeue_xfer(struct dw_i3c_master *master,
> - struct dw_i3c_xfer *xfer)
> +static void dw_i3c_master_dequeue_xfer_locked(struct dw_i3c_master *master,
> + struct dw_i3c_xfer *xfer)
> {
> - unsigned long flags;
> -
> - spin_lock_irqsave(&master->xferqueue.lock, flags);
> if (master->xferqueue.cur == xfer) {
> u32 status;
>
> @@ -439,6 +436,15 @@ static void dw_i3c_master_dequeue_xfer(struct dw_i3c_master *master,
> } else {
> list_del_init(&xfer->node);
> }
> +}
> +
> +static void dw_i3c_master_dequeue_xfer(struct dw_i3c_master *master,
> + struct dw_i3c_xfer *xfer)
> +{
> + unsigned long flags;
> +
> + spin_lock_irqsave(&master->xferqueue.lock, flags);
> + dw_i3c_master_dequeue_xfer_locked(master, xfer);
> spin_unlock_irqrestore(&master->xferqueue.lock, flags);
> }
>
> @@ -494,7 +500,7 @@ static void dw_i3c_master_end_xfer_locked(struct dw_i3c_master *master, u32 isr)
> complete(&xfer->comp);
>
> if (ret < 0) {
> - dw_i3c_master_dequeue_xfer(master, xfer);
> + dw_i3c_master_dequeue_xfer_locked(master, xfer);
> writel(readl(master->regs + DEVICE_CTRL) | DEV_CTRL_RESUME,
> master->regs + DEVICE_CTRL);
> }
Acked-by: Vitor Soares <vitor.soares@synopsys.com>
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2019-01-25 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 7:29 [PATCH] i3c: master: dw: fix deadlock Jisheng Zhang
2019-01-25 11:55 ` vitor [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=54d8926f-f0fd-c2c7-1b8a-dce1384892b7@synopsys.com \
--to=vitor.soares@synopsys.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=bbrezillon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox