From: Shawn Lin <shawn.lin@rock-chips.com>
To: Jialing Fu <jlfu@marvell.com>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: shawn.lin@rock-chips.com, linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH] mmc: core: fix race condition in mmc_wait_data_done
Date: Fri, 28 Aug 2015 21:51:28 +0800 [thread overview]
Message-ID: <55E06760.8020308@rock-chips.com> (raw)
In-Reply-To: <1243788837884e859a8959cf8265125c@SC-EXCH04.marvell.com>
在 2015/8/28 18:22, Jialing Fu 写道:
>
> [...]
>
>>>> Hi, ulf
>>>>
>>>> We find this bug on Intel-C3230RK platform for very small probability.
>>>>
>>>> Whereas I can easily reproduce this case if I add a mdelay(1) or
>>>> longer delay as Jialing did.
>>>>
>>>> This patch seems useful to me. Should we push it forward? :)
>>>
>>>
>>> It seems like a very good idea!
>>>
>>> Should we add a fixes tag to it?
>>
>>
>> That's cool, but how to add a fixes tag?
>>
>> [Fixes] mmc: core: fix race condition in mmc_wait_data_done ? :)
>>
>
> A fixes tag points to an old commit which introduced the bug. If we can't find one, we can add a Cc tag to "stable". Just search the git log and you will find examples.
>
> Like add one line as below?
> Fixes: 2220eedfd7ae ("mmc: fix async request mechanism for sequential read scenarios")
>
That's it, Jialing. From my git blame, seems this bug has been
introduced for a long time, but I feel strange that no one had captured
it before you did.
Anyway, I will add a fixes tag and send v2 ASAP. :)
>
> Kind regards
> Uffe
>
--
Best Regards
Shawn Lin
next prev parent reply other threads:[~2015-08-28 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 3:13 [RESEND PATCH] mmc: core: fix race condition in mmc_wait_data_done Shawn Lin
2015-08-28 3:25 ` Shawn Lin
2015-08-28 8:55 ` Ulf Hansson
2015-08-28 9:53 ` Shawn Lin
2015-08-28 10:09 ` Ulf Hansson
2015-08-28 10:22 ` Jialing Fu
2015-08-28 13:51 ` Shawn Lin [this message]
2015-08-31 2:03 ` ~RE: " Jialing Fu
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=55E06760.8020308@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=jlfu@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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