Re: CONFIG_MARKERS

[Frank Ch. Eigler]

Jon Masters <jcm@xxxxxxxxxx> writes:

> 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? [...]

I can't seem to find any discussion about this aspect.  If this is the
intent, it seems misguided to me.  There may instead be a relationship
to TAINT_FORCED_{RMMOD,MODULE}.  Mathieu?

- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/