From: Jon Masters <jcm@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Subject: CONFIG_MARKERS
Date: Tue, 22 Jan 2008 14:13:55 -0500 [thread overview]
Message-ID: <1201029235.18144.62.camel@perihelion> (raw)
Yo,
I notice in module.c:
#ifdef CONFIG_MARKERS
if (!mod->taints)
marker_update_probe_range(mod->markers,
mod->markers + mod->num_markers, NULL, NULL);
#endif
Is this an attempt to not set a marker for proprietary modules? If so,
then this really should be the following conditional instead, because,
really we're not guaranteeing there won't be other taints (e.g. in RHEL
we already have the module signing patch, and then there's also the
TAINT_FORCED_MODULE, which arguably isn't a "taint" for markers):
#ifdef CONFIG_MARKERS
if (!(mod->taints & TAINT_PROPRIETARY_MODULE))
marker_update_probe_range(mod->markers,
mod->markers + mod->num_markers, NULL, NULL);
#endif
Or am I missing something?
Jon.
next reply other threads:[~2008-01-22 19:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 19:13 Jon Masters [this message]
2008-01-23 3:00 ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23 3:10 ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 4:17 ` CONFIG_MARKERS Jon Masters
2008-01-23 13:14 ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23 14:48 ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 15:01 ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 16:33 ` CONFIG_MARKERS Jon Masters
2008-01-23 17:11 ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-24 5:25 ` CONFIG_MARKERS Valdis.Kletnieks
2008-01-24 6:19 ` CONFIG_MARKERS Jon Masters
2008-01-24 12:47 ` [PATCH] Linux Kernel Markers Support for Proprierary Modules Mathieu Desnoyers
2008-01-24 18:27 ` Valdis.Kletnieks
2008-01-24 20:35 ` Jon Masters
2008-01-25 1:27 ` Rusty Russell
2008-01-25 7:56 ` Jan Engelhardt
2008-01-25 8:03 ` Valdis.Kletnieks
2008-01-25 16:32 ` Alan Cox
2008-01-25 15:31 ` Jon Masters
2008-01-25 16:01 ` Jan Engelhardt
2008-01-26 3:27 ` Rusty Russell
2008-01-26 4:21 ` Jon Masters
2008-01-27 10:48 ` Jan Engelhardt
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=1201029235.18144.62.camel@perihelion \
--to=jcm@redhat.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
all inboxes | Powered by JetHome®