[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200901291814.19787.rusty@rustcorp.com.au>
Date: Thu, 29 Jan 2009 18:14:19 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: Arjan van de Ven <arjan@...radead.org>
Cc: linux-kernel@...r.kernel.org,
Shawn Bohrer <shawn.bohrer@...il.com>,
Jon Masters <jonathan@...masters.org>
Subject: Re: [PATCH 5/6] module: make modversion_info contain a pointer, not an array.
On Thursday 29 January 2009 09:11:14 Arjan van de Ven wrote:
> On Thu, 29 Jan 2009 08:59:40 +1030
> Rusty Russell <rusty@...tcorp.com.au> wrote:
>
> > On Thursday 29 January 2009 01:22:31 Arjan van de Ven wrote:
> > > On Thu, 29 Jan 2009 00:05:52 +1030
> > > Rusty Russell <rusty@...tcorp.com.au> wrote:
> > >
> > > >
> > > > With allmodconfig (minus non-building modules) on 32-bit x86:
> > > > Total size of modules before: 60009790 bytes
> > > > Total size of modules after: 55927866 bytes
> > > >
> > > > Saving 7% of module size for CONFIG_MODVERSIONS=y; and these
> > > > sections are kept resident as well.
> > > >
> > >
> > > that reminds me.. can we just simplify MODVERSIONS to be a md5sum
> > > (or sha1 whatver) of the .config file in the VERMAGIC ?
> > > it's a lot more reliable in detecting incompatibilities, and a lot
> > > less space consumed.
> >
> > Unfortunately people really seem to want the finer granularity that
> > MODVERSIONS (sometimes) provides :( I've tried killing it off
> > several times, and always failed.
>
> but we could just stick the result in VERMAGIC right?
> rather than tacking it to every symbol.
Sure, but who would use it? If you add a driver I don't want my modules to fail.
Confused,
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/
Powered by blists - more mailing lists