[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1407764272.git.jani.nikula@intel.com>
Date: Mon, 11 Aug 2014 16:52:18 +0300
From: Jani Nikula <jani.nikula@...el.com>
To: linux-kernel@...r.kernel.org, intel-gfx@...ts.freedesktop.org
Cc: Rusty Russell <rusty@...tcorp.com.au>,
Jean Delvare <khali@...ux-fr.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Li Zhong <zhong@...ux.vnet.ibm.com>,
Jon Mason <jon.mason@...el.com>,
Daniel Vetter <daniel.vetter@...ll.ch>, jani.nikula@...el.com
Subject: [PATCH 0/4] module: add support for unsafe, tainting parameters
This is a generic version of Daniel's patch [1] letting us have unsafe
module parameters (experimental, debugging, testing, etc.) that taint
the kernel when set. Quoting Daniel,
"""
Users just love to set random piles of options since surely enabling all
the experimental stuff helps. Later on we get bug reports because it all
fell apart.
Even more fun when it's labelled a regression when some change only just
made the feature possible (e.g. stolen memory fixes suddenly making fbc
possible).
Make it clear that users are playing with fire here.
"""
Patches 1-3 add the core functionality, patch 4 is our use case as an
example.
BR,
Jani.
[1] http://lkml.kernel.org/r/1394011994-30604-1-git-send-email-daniel.vetter@ffwll.ch
Jani Nikula (4):
module: rename KERNEL_PARAM_FL_NOARG to avoid confusion
module: make it possible to have unsafe, tainting module params
module: add module_param_unsafe and module_param_named_unsafe
drm/i915: taint the kernel if unsafe module parameters are set
drivers/gpu/drm/i915/i915_params.c | 8 ++---
drivers/tty/serial/8250/8250_core.c | 2 +-
include/linux/moduleparam.h | 64 +++++++++++++++++++++++++++++++------
kernel/module.c | 2 +-
kernel/params.c | 17 ++++++++--
security/apparmor/lsm.c | 4 +--
6 files changed, 76 insertions(+), 21 deletions(-)
--
1.9.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/
Powered by blists - more mailing lists