linux-kernel - [PATCH 0/3] amba/coresight: make non-modular code explicitly non-modular

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]

Date:	Sun, 11 Oct 2015 21:35:44 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	<linux-arm-kernel@...ts.infradead.org>
CC:	<linux-kernel@...r.kernel.org>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Alexandre Courbot <gnurou@...il.com>,
	Mathieu Poirier <mathieu.poirier@...aro.org>,
	Russell King <linux@....linux.org.uk>,
	Stephen Warren <swarren@...dotorg.org>,
	Thierry Reding <thierry.reding@...il.com>,
	<linux-tegra@...r.kernel.org>
Subject: [PATCH 0/3] amba/coresight: make non-modular code explicitly non-modular

In a previous merge window, we made changes to allow better
delineation between modular and non-modular code in commit
0fd972a7d91d6e15393c449492a04d94c0b89351 ("module: relocate module_init
from init.h to module.h").  This allows us to now ensure module code
looks modular and non-modular code does not accidentally look modular
just to avoid suffering build breakage.

Here we target code that is, by nature of their Makefile and/or
Kconfig settings, only available to be built-in, but implicitly
presenting itself as being possibly modular by way of using modular
headers, macros, and functions.

The goal here is to remove that illusion of modularity from these
files, but in a way that leaves the actual runtime unchanged.
In doing so, we remove code that has never been tested and adds
no value to the tree.  And we continue the process of expecting a
level of consistency between the Kconfig/Makefile of code and the
code in use itself.

The coresight drivers make extensive use of module_amba_driver, hence
why this is all grouped together. Build tested on the latest linux-next,
for ARCH=arm.

Note that the coresight drivers could in theory be unbound prior to
this commit, but there doesn't seem to be any case where that would
make sense, so we explicitly disable that now that we have deleted
the .remove functions that the unbind would have called.

Paul.
--

Cc: Alexandre Courbot <gnurou@...il.com>
Cc: Mathieu Poirier <mathieu.poirier@...aro.org>
Cc: Russell King <linux@....linux.org.uk>
Cc: Stephen Warren <swarren@...dotorg.org>
Cc: Thierry Reding <thierry.reding@...il.com>
Cc: linux-arm-kernel@...ts.infradead.org
Cc: linux-tegra@...r.kernel.org

Paul Gortmaker (3):
  amba: create builtin_amba_driver to avoid registration boilerplate
  drivers/hwtracing: make coresight-* explicitly non-modular
  drivers/amba: make tegra-ahb.c explicitly non-modular

 drivers/amba/tegra-ahb.c                           |  9 ++-----
 drivers/hwtracing/coresight/coresight-etb10.c      | 26 +++++--------------
 drivers/hwtracing/coresight/coresight-etm3x.c      | 29 ++++++---------------
 drivers/hwtracing/coresight/coresight-etm4x.c      | 19 +++-----------
 drivers/hwtracing/coresight/coresight-funnel.c     | 25 +++++-------------
 .../coresight/coresight-replicator-qcom.c          | 19 +++-----------
 drivers/hwtracing/coresight/coresight-replicator.c | 30 +++++-----------------
 drivers/hwtracing/coresight/coresight-tmc.c        | 28 +++++---------------
 drivers/hwtracing/coresight/coresight-tpiu.c       | 25 +++++-------------
 drivers/hwtracing/coresight/coresight.c            |  3 ---
 drivers/hwtracing/coresight/of_coresight.c         |  1 -
 include/linux/amba/bus.h                           |  9 +++++++
 12 files changed, 60 insertions(+), 163 deletions(-)

-- 
2.6.1

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