From: Randy Dunlap <rdunlap@xenotime.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>, Greg KH <greg@kroah.com>,
Debian kernel maintainers <debian-kernel@lists.debian.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree
Date: Mon, 24 Oct 2011 07:57:03 -0700 [thread overview]
Message-ID: <4EA57CBF.2050901@xenotime.net> (raw)
In-Reply-To: <1319461948.31243.31.camel@deadeye>
On 10/24/11 06:12, Ben Hutchings wrote:
> Use of the GPL or a compatible licence doesn't necessarily make the code
> any good. We already consider staging modules to be suspect, and this
> should also be true for out-of-tree modules which may receive very
> little review.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> Debian has been carrying this for the last few kernel versions. The
> recent thread '[RFC] virtualbox tainting.' and discussions at KS suggest
> that this might be more generally useful.
>
> Ben.
>
> include/linux/kernel.h | 1 +
> kernel/module.c | 5 +++++
> kernel/panic.c | 2 ++
> scripts/mod/modpost.c | 7 +++++++
> 4 files changed, 15 insertions(+), 0 deletions(-)
Hi,
Please add 'O' to Documentation/oops-tracing.txt.
Thanks.
> diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> index 46ac9a5..2c05967 100644
> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -369,6 +369,7 @@ extern enum system_states {
> #define TAINT_WARN 9
> #define TAINT_CRAP 10
> #define TAINT_FIRMWARE_WORKAROUND 11
> +#define TAINT_OOT_MODULE 12
>
> extern const char hex_asc[];
> #define hex_asc_lo(x) hex_asc[((x) & 0x0f)]
> diff --git a/kernel/module.c b/kernel/module.c
> index 04379f92..c0872f1 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -2487,6 +2487,9 @@ static int check_modinfo(struct module *mod, struct load_info *info)
> return -ENOEXEC;
> }
>
> + if (!get_modinfo(info, "intree"))
> + add_taint_module(mod, TAINT_OOT_MODULE);
> +
> if (get_modinfo(info, "staging")) {
> add_taint_module(mod, TAINT_CRAP);
> printk(KERN_WARNING "%s: module is from the staging directory,"
> @@ -3257,6 +3260,8 @@ static char *module_flags(struct module *mod, char *buf)
> buf[bx++] = '(';
> if (mod->taints & (1 << TAINT_PROPRIETARY_MODULE))
> buf[bx++] = 'P';
> + else if (mod->taints & (1 << TAINT_OOT_MODULE))
> + buf[bx++] = 'O';
> if (mod->taints & (1 << TAINT_FORCED_MODULE))
> buf[bx++] = 'F';
> if (mod->taints & (1 << TAINT_CRAP))
> diff --git a/kernel/panic.c b/kernel/panic.c
> index d7bb697..b2659360 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -177,6 +177,7 @@ static const struct tnt tnts[] = {
> { TAINT_WARN, 'W', ' ' },
> { TAINT_CRAP, 'C', ' ' },
> { TAINT_FIRMWARE_WORKAROUND, 'I', ' ' },
> + { TAINT_OOT_MODULE, 'O', ' ' },
> };
>
> /**
> @@ -194,6 +195,7 @@ static const struct tnt tnts[] = {
> * 'W' - Taint on warning.
> * 'C' - modules from drivers/staging are loaded.
> * 'I' - Working around severe firmware bug.
> + * 'O' - Out-of-tree module has been loaded.
> *
> * The string is overwritten by the next call to print_tainted().
> */
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index a509ff8..2bd594e 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -1849,6 +1849,12 @@ static void add_header(struct buffer *b, struct module *mod)
> buf_printf(b, "};\n");
> }
>
> +static void add_intree_flag(struct buffer *b, int is_intree)
> +{
> + if (is_intree)
> + buf_printf(b, "\nMODULE_INFO(intree, \"Y\");\n");
> +}
> +
> static void add_staging_flag(struct buffer *b, const char *name)
> {
> static const char *staging_dir = "drivers/staging";
> @@ -2169,6 +2175,7 @@ int main(int argc, char **argv)
> buf.pos = 0;
>
> add_header(&buf, mod);
> + add_intree_flag(&buf, !external_module);
> add_staging_flag(&buf, mod->name);
> err |= add_versions(&buf, mod);
> add_depends(&buf, mod, modules);
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-10-24 14:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 13:12 [PATCH] module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree Ben Hutchings
2011-10-24 13:58 ` Dave Jones
2011-10-24 14:57 ` Randy Dunlap [this message]
2011-10-25 3:56 ` Rusty Russell
2011-10-25 9:52 ` Ben Hutchings
2011-10-25 15:38 ` Nick Bowler
2011-10-25 16:05 ` Ben Hutchings
2011-10-25 16:51 ` Nick Bowler
2011-10-25 20:04 ` Greg KH
2011-10-25 20:17 ` Dave Jones
2011-10-25 20:54 ` Greg KH
2011-10-26 13:08 ` Nick Bowler
2011-10-27 1:11 ` Rusty Russell
2011-10-27 1:55 ` Dave Jones
2011-10-31 1:30 ` Rusty Russell
2011-10-27 5:49 ` Greg KH
2011-10-26 4:16 ` Rusty Russell
2011-10-26 6:15 ` Mathieu Desnoyers
2011-10-25 1:37 ` Greg KH
2011-12-12 21:40 ` Luis R. Rodriguez
2011-12-12 21:58 ` Ben Hutchings
2011-12-12 22:47 ` Luis R. Rodriguez
2011-12-12 22:49 ` Luis R. Rodriguez
2011-12-13 5:02 ` Ben Hutchings
2011-12-14 16:20 ` [RFC] modpost: add option to allow external modules to avoid taint John W. Linville
2011-12-14 16:52 ` Ben Hutchings
2011-12-14 17:39 ` John W. Linville
[not found] ` <87mxatp3ty.fsf@rustcorp.com.au>
2011-12-16 4:39 ` Ben Hutchings
2011-12-19 5:45 ` Rusty Russell
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=4EA57CBF.2050901@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=debian-kernel@lists.debian.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).