linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Jialing Fu <jlfu@marvell.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 12:09:13 +0200	[thread overview]
Message-ID: <CAPDyKFqYDdwvTCw3oKhkxqu9zmTAC8osLgd6eC4zDY7JOMGGPQ@mail.gmail.com> (raw)
In-Reply-To: <55E02F7C.1020204@rock-chips.com>

[...]

>>> 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.

Kind regards
Uffe

  reply	other threads:[~2015-08-28 10:09 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 [this message]
2015-08-28 10:22         ` Jialing Fu
2015-08-28 13:51           ` Shawn Lin
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=CAPDyKFqYDdwvTCw3oKhkxqu9zmTAC8osLgd6eC4zDY7JOMGGPQ@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=jlfu@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shawn.lin@rock-chips.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;
as well as URLs for NNTP newsgroup(s).