All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-mmc@vger.kernel.org, Dmitry Shmidt <dimitrysh@google.com>,
	Maxim Levitsky <maximlevitsky@gmail.com>,
	stable@kernel.org
Subject: Re: [PATCH] mmc: fix CONFIG_MMC_UNSAFE_RESUME regression
Date: Tue, 08 Mar 2011 16:56:50 -0500	[thread overview]
Message-ID: <m3hbbdp97h.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <1299619922-22220-1-git-send-email-ohad@wizery.com> (Ohad Ben-Cohen's message of "Tue, 8 Mar 2011 23:32:02 +0200")

Hi Ohad,

On Tue, Mar 08 2011, Ohad Ben-Cohen wrote:
> 30201e7 allowed skipping detection of nonremovable cards on
> mmc_rescan(). The intention was to only skip detection of hardwired
> cards that cannot be removed, so make sure this is indeed the
> case by directly checking for (lack of) MMC_CAP_NONREMOVABLE, instead
> of using mmc_card_is_removable(), which is overloaded with
> CONFIG_MMC_UNSAFE_RESUME semantics.
>
> Reported-and-tested-by: Dmitry Shmidt <dimitrysh@google.com>
> Reported-and-tested-by: Maxim Levitsky <maximlevitsky@gmail.com>
> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
> Cc: <stable@kernel.org>
> ---
> Based on linux-2.6.git master, as this should probably go to Linus.
>
>  drivers/mmc/core/core.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 6625c05..150b5f3 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -1529,7 +1529,7 @@ void mmc_rescan(struct work_struct *work)
>  	 * still present
>  	 */
>  	if (host->bus_ops && host->bus_ops->detect && !host->bus_dead
> -	    && mmc_card_is_removable(host))
> +	    && !(host->caps & MMC_CAP_NONREMOVABLE))
>  		host->bus_ops->detect(host);
>  
>  	/*

Thanks, I will send this to Linus for .38 final.

I have removed the stable@ tag, because the patch causing this
regression was introduced in .38-rc1 -- it has not been part of
any released kernel.  So, as long as we fix it before .38 releases
in a week, there's no need to involve stable@.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-03-08 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 21:32 [PATCH] mmc: fix CONFIG_MMC_UNSAFE_RESUME regression Ohad Ben-Cohen
2011-03-08 21:56 ` Chris Ball [this message]
2011-03-08 22:20   ` Ohad Ben-Cohen

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=m3hbbdp97h.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=dimitrysh@google.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=ohad@wizery.com \
    --cc=stable@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 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.