mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: Fabien DESSENNE <fabien.dessenne@st.com>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	Benjamin GAIGNARD <benjamin.gaignard@st.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/2] bdisp: Fix a possible sleep-in-atomic bug in bdisp_hw_reset
Date: Tue, 19 Dec 2017 21:57:15 +0800	[thread overview]
Message-ID: <0551d83c-47c6-e3e0-77fd-f861c6878cbe@gmail.com> (raw)
In-Reply-To: <b526fa1a-e670-4abe-078c-2c7c5af9a42c@st.com>


On 2017/12/19 18:43, Fabien DESSENNE wrote:
> Hi,
>
>
> On 16/12/17 12:54, Jia-Ju Bai wrote:
>> The driver may sleep under a spinlock.
>> The function call path is:
>> bdisp_device_run (acquire the spinlock)
>>     bdisp_hw_reset
>>       msleep --> may sleep
>>
>> To fix it, readl_poll_timeout_atomic is used to replace msleep.
>>
>> This bug is found by my static analysis tool(DSAC) and
>> checked by my code review.
>>
>> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
>> ---
>>    drivers/media/platform/sti/bdisp/bdisp-hw.c |   16 ++++++++--------
>>    1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/media/platform/sti/bdisp/bdisp-hw.c b/drivers/media/platform/sti/bdisp/bdisp-hw.c
>> index b7892f3..e94a371 100644
>> --- a/drivers/media/platform/sti/bdisp/bdisp-hw.c
>> +++ b/drivers/media/platform/sti/bdisp/bdisp-hw.c
>> @@ -5,6 +5,7 @@
>>     */
>>    
>>    #include <linux/delay.h>
> This delay.h include is no more needed, remove it.
>
>> +#include <linux/iopoll.h>
>>    
>>    #include "bdisp.h"
>>    #include "bdisp-filter.h"
>> @@ -366,7 +367,7 @@ struct bdisp_filter_addr {
>>     */
>>    int bdisp_hw_reset(struct bdisp_dev *bdisp)
>>    {
>> -	unsigned int i;
>> +	u32 tmp;
>>    
>>    	dev_dbg(bdisp->dev, "%s\n", __func__);
>>    
>> @@ -379,15 +380,14 @@ int bdisp_hw_reset(struct bdisp_dev *bdisp)
>>    	writel(0, bdisp->regs + BLT_CTL);
>>    
>>    	/* Wait for reset done */
>> -	for (i = 0; i < POLL_RST_MAX; i++) {
>> -		if (readl(bdisp->regs + BLT_STA1) & BLT_STA1_IDLE)
>> -			break;
>> -		msleep(POLL_RST_DELAY_MS);
>> -	}
>> -	if (i == POLL_RST_MAX)
> As recommended by Mauro, please add this comment:
> Despite the large timeout, most of the time the reset happens without
> needing any delays
>
>> +	if (readl_poll_timeout_atomic(bdisp->regs + BLT_STA1, tmp,
>> +		(tmp & BLT_STA1_IDLE), POLL_RST_DELAY_MS,
>> +			POLL_RST_DELAY_MS * POLL_RST_MAX)) {
> read_poll_timeout expects US timings, not MS.
>
>>    		dev_err(bdisp->dev, "Reset timeout\n");
>> +		return -EAGAIN;
>> +	}
>>    
>> -	return (i == POLL_RST_MAX) ? -EAGAIN : 0;
>> +	return 0;
>>    }
>>    
>>    /**

Hi,

Okay, I have submitted a new patch according to your advice :)


Thanks,
Jia-Ju Bai

      reply	other threads:[~2017-12-19 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-16 11:54 Jia-Ju Bai
2017-12-19 10:43 ` Fabien DESSENNE
2017-12-19 13:57   ` Jia-Ju Bai [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=0551d83c-47c6-e3e0-77fd-f861c6878cbe@gmail.com \
    --to=baijiaju1990@gmail.com \
    --cc=benjamin.gaignard@st.com \
    --cc=fabien.dessenne@st.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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

all inboxes | Powered by JetHome®