linux-kernel - Re: [PATCH 5/6] module: make modversion_info contain a pointer, not an array.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200902101357.34716.rusty@rustcorp.com.au>
Date:	Tue, 10 Feb 2009 13:57:34 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Shawn Bohrer <shawn.bohrer@...il.com>
Cc:	linux-kernel@...r.kernel.org, Jon Masters <jonathan@...masters.org>
Subject: Re: [PATCH 5/6] module: make modversion_info contain a pointer, not an array.

On Tuesday 10 February 2009 04:20:50 Shawn Bohrer wrote:
> This also results in a taint flag of 3.  So I'm thinking the regression
> here is that somewhere between 2.6.25 (I know openSUSE 11 worked too)
> and 2.6.27 the kernel stopped allowing modules to load if they didn't
> build with modversion support and the kernel was built with
> CONFIG_MODVERSIONS=y.

Before 2.6.26, the kernel ignored the vermagic field when
CONFIG_MODVERSIONS=y.  I changed it to only ignore vermagic *if* there
were CRCs.

If you use modprobe --force, you should be able to load a non-modversions
module into a modversions kernel.

> > And anyway, what was the symbol name which is over 56 characters long which
> > started this?
> 
> Yeah, that is an interesting question isn't it?  Let me just say that
> namespaces and name mangling make it really easy to have names longer
> than 56 characters.

Yes, C++.  This is one reason we don't support it.

Hope that helps,
Rusty.
--
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/