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.1375279948.git.viresh.kumar@linaro.org>
Date:	Wed, 31 Jul 2013 19:49:09 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	rjw@...k.pl
Cc:	linaro-kernel@...ts.linaro.org, patches@...aro.org,
	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org, arnd.bergmann@...aro.org,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE

CPUFreq core does following at multiple places:
module_{get|put}(cpufreq_driver->owner)).

This is done to make sure module doesn't get unloaded if it is currently in use.
This will work only if the .owner field of cpufreq driver is initialized with a
valid pointer.

This field wasn't initialized for many cpufreq driver, lets initialize it with
THIS_MODULE.

Rebased over: v3.11-rc3 and pushed here:

https://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/cpufreq-fix-owner

Viresh Kumar (15):
  cpufreq: arm_big_little: initialize .owner field with THIS_MODULE
  cpufreq: cpufreq-cpu0: initialize .owner field with THIS_MODULE
  cpufreq: davinci: initialize .owner field with THIS_MODULE
  cpufreq: dbx500: initialize .owner field with THIS_MODULE
  cpufreq: exynos: initialize .owner field with THIS_MODULE
  cpufreq: imx6q: initialize .owner field with THIS_MODULE
  cpufreq: integrator: initialize .owner field with THIS_MODULE
  cpufreq: omap: initialize .owner field with THIS_MODULE
  cpufreq: pxa: initialize .owner field with THIS_MODULE
  cpufreq: s3c24xx: initialize .owner field with THIS_MODULE
  cpufreq: s5pv210: initialize .owner field with THIS_MODULE
  cpufreq: sa11**: initialize .owner field with THIS_MODULE
  cpufreq: SPEAr: initialize .owner field with THIS_MODULE
  cpufreq: Tegra: initialize .owner field with THIS_MODULE
  cpufreq: Unicore: initialize .owner field with THIS_MODULE

 drivers/cpufreq/arm_big_little.c     | 1 +
 drivers/cpufreq/cpufreq-cpu0.c       | 1 +
 drivers/cpufreq/davinci-cpufreq.c    | 1 +
 drivers/cpufreq/dbx500-cpufreq.c     | 1 +
 drivers/cpufreq/exynos-cpufreq.c     | 1 +
 drivers/cpufreq/exynos5440-cpufreq.c | 1 +
 drivers/cpufreq/imx6q-cpufreq.c      | 1 +
 drivers/cpufreq/integrator-cpufreq.c | 1 +
 drivers/cpufreq/omap-cpufreq.c       | 1 +
 drivers/cpufreq/pxa2xx-cpufreq.c     | 1 +
 drivers/cpufreq/pxa3xx-cpufreq.c     | 1 +
 drivers/cpufreq/s3c24xx-cpufreq.c    | 1 +
 drivers/cpufreq/s5pv210-cpufreq.c    | 1 +
 drivers/cpufreq/sa1100-cpufreq.c     | 1 +
 drivers/cpufreq/sa1110-cpufreq.c     | 1 +
 drivers/cpufreq/spear-cpufreq.c      | 1 +
 drivers/cpufreq/tegra-cpufreq.c      | 1 +
 drivers/cpufreq/unicore2-cpufreq.c   | 1 +
 18 files changed, 18 insertions(+)

-- 
1.7.12.rc2.18.g61b472e

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ