The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Yauhen Kharuzhy <jekhor@gmail.com>
Cc: linux-kernel@vger.kernel.org, Yauhen Kharuzhy <jekhor@gmail.com>
Subject: Re: [PATCH] MMC: Fix race condition in resume/card detect code
Date: Sat, 18 Oct 2008 19:11:47 +0200	[thread overview]
Message-ID: <20081018191147.00327019@mjolnir.drzeus.cx> (raw)
In-Reply-To: <1224173376-25829-1-git-send-email-jekhor@gmail.com>

On Thu, 16 Oct 2008 19:09:36 +0300
Yauhen Kharuzhy <jekhor@gmail.com> wrote:

> When device wakes up by card change interrupt and MMC_UNSAFE_RESUME is
> enabled then race condition between mmc_rescan() and
> mmc_resume()/mmc_sd_resume() appeared.
> 
> Resume functions can sleep into mmc_remove_card() and at this time
> mmc_rescan() can be called by delayed work handler. Double-free of
> kobject or double-remove of host->card can be result of this.
> 
> This patch adds an mutex which deny simultaneous executing of
> mmc_sd_resume()/mmc_resume() and mmc_rescan() functions. Probably, it is
> not right way.
> 
> Signed-off-by: Yauhen Kharuzhy <jekhor@gmail.com>
> ---

Can't we just ask the PM layer if this device is currently resuming,
and if so ignore card notifications from the driver?

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

  reply	other threads:[~2008-10-18 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 16:09 [PATCH] MMC: Fix race condition in resume/card detect code Yauhen Kharuzhy
2008-10-18 17:11 ` Pierre Ossman [this message]
2008-10-19 16:04   ` Yauhen Kharuzhy
2008-10-19 16:32     ` Yauhen Kharuzhy
2008-10-20 19:41   ` Yauhen Kharuzhy
2008-10-20 20:47     ` J.A. Magallón
2008-10-26 11:47     ` Pierre Ossman

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=20081018191147.00327019@mjolnir.drzeus.cx \
    --to=drzeus-mmc@drzeus.cx \
    --cc=jekhor@gmail.com \
    --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