linux-kernel - [PATCH v2 0/3] mmc: fixes for aggressive clock gating framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <cover.1313664897.git.mika.westerberg@linux.intel.com>
Date:	Thu, 18 Aug 2011 15:23:46 +0300
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	linux-mmc@...r.kernel.org
Cc:	cjb@...top.org, linus.walleij@...aro.org,
	linux-kernel@...r.kernel.org,
	Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: [PATCH v2 0/3] mmc: fixes for aggressive clock gating framework

Hi,

This is an updated series which should fix few races seen when aggressive
clock gating is active. The first patch actually just renames the gating
functions to make their use-cases a bit more clear.

Second and third patches fix the races itself.

Previous version of the series can be seen here
	http://article.gmane.org/gmane.linux.kernel.mmc/9611

Changes to previous version:
	* rename clock gating functions
	* use mmc_host_clk_hold() and mmc_host_clk_release() to protect the
	  ios updates
	* use non-reentrant workqueue instead of the default

Please review, thanks.

Mika Westerberg (3):
  mmc: rename mmc_host_clk_{ungate|gate} to mmc_host_clk_{hold|release}
  mmc: prevent aggressive clock gating to race with ios updates
  mmc: use non-reentrant workqueue for clock gating

 drivers/mmc/core/core.c |   35 +++++++++++++++++++++++++++++++----
 drivers/mmc/core/host.c |   12 ++++++------
 drivers/mmc/core/host.h |    8 ++++----
 3 files changed, 41 insertions(+), 14 deletions(-)

-- 
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/