Re: RFC: virtualbox tainting.
From: Dave Jones
Date: Thu Oct 06 2011 - 16:03:22 EST
On Thu, Oct 06, 2011 at 03:53:42PM -0400, Valdis.Kletnieks@xxxxxx wrote:
> On Thu, 06 Oct 2011 15:50:07 EDT, Dave Jones said:
> > I feel a bit dirty overloading TAINT_CRAP (even if the name is apropos).
> > Should I introduce a TAINT_OUT_OF_TREE perhaps instead ?
> That would fix my biggest issue with the patch - it's a slippery slope. But if
> we bite the bullet and go straight to the bottom of the slope with an
> OUT_OF_TREE taint, I'd be happy with that.
> Is there a good way to identify at modprobe time if a module is in-tree or
Not easily from within the kernel. (and doing it in userspace is pointless,
as out of tree modules could just add themselves to the list of 'clean' modules)
We actually used to do something in RHEL a few years ago where we gpg signed the
modules we were building, for pretty much this reason. (also useful for spotting when
for eg, an IHV replaces ext3.ko with their own version in their preloads).
A bit overkill though compared to just having a hardcoded list of offenders in the kernel.
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/