Re: Speaking of kernel modules versioning...

[Josko Plazonic <plazonic Math Princeton EDU>]

At the time I suggested to Vincent, in a private E-mail, to try 
fixscript.  I don't know of the outcome but he seemed pleased.

fixscript is a bash script written for one of linmodem projects whose 
purpose is to relabel relevant symbols in a module to match a different 
(but similar!) kernel.

Google will quickly give you a link to a copy of it.  I have needed it 
for exactly the same reason as you do. Sample usage is something like:
fixscript module-for-15.0.4.o module-for-15.0.4.cisco.1.o
or something like that.

Josko P.


Brian Long wrote:

> Did you ever get an answer to this?  We're patching -15.0.4 with the
> 32-bit UID fix for AMD64, but we like to keep our kernels the same
> across the i386 and AMD64 architectures.  EMC Powerpath will load with
> -15.0.4 but not with our -15.0.4.cisco.1 kernel.
>
> Any ideas how we can fake EMC Powerpath into loading?  Is it the
> MOD_VERSION or some such inside the kernel config?
>
> /Brian/
>
> On Wed, 2004-07-14 at 13:45, Vincent Cojot wrote:
>
> > Just noticed this after my previous post:
> >
> > [root thorbardin kernel]# pwd
> > /etc/vx/kernel
> >
> > [root thorbardin kernel]# ls -la vxspec.o.*
> > -rw-r--r--    1 root     root         8628 May 13 02:33 vxspec.o.SMP-HIGHMEM64G.2.4.21-15.ELhugemem
> > -rw-r--r--    1 root     root         8628 May 13 02:33 vxspec.o.SMP-HIGHMEM64G.2.4.21-15.ELsmp
> > -rw-r--r--    1 root     root         8628 May 13 02:33 vxspec.o.SMP-HIGHMEM64G.2.4.21-4.ELhugemem
> > -rw-r--r--    1 root     root         8628 May 13 02:33 vxspec.o.SMP-HIGHMEM64G.2.4.21-4.ELsmp
> > -rw-r--r--    1 root     root         8257 May 13 02:33 vxspec.o.UP-HIGHMEM4G.2.4.21-15.EL
> > -rw-r--r--    1 root     root         8257 May 13 02:33 vxspec.o.UP-HIGHMEM4G.2.4.21-4.EL
> >
> > [root thorbardin kernel]# objdump -w -t vxspec.o.*|grep printk_
> > 00000000         *UND*  00000000 printk_Rsmp_1b7d4074
> > 00000000         *UND*  00000000 printk_Rsmp_1b7d4074
> > 00000000         *UND*  00000000 printk_Rsmp_1b7d4074
> > 00000000         *UND*  00000000 printk_Rsmp_1b7d4074
> > 00000000         *UND*  00000000 printk_R1b7d4074
> > 00000000         *UND*  00000000 printk_R1b7d4074
> >
> > So all of Veritas kernel modules for different versions of RHEL3 seem to 
> > have the same kernel name mangling.
> >
> > Therefore, it seems that RH's kernel are able to have a consistent symbol 
> > versioning in order to let ISV's binary modules load under the RH-built 
> > kernels...
> >
> > Does anyone know what it would take to let my 15.0.32 (15.0.3-based) 
> > custom-built kernel have the same kernel module symbols 'name mangling' in 
> > order to have VxVM modules load successfully on my custom kernels?
> > Is that doable at all?
> >
> > To rebuild my kernel, all I did was to add a patch to the spec file and 
> > rpmbuild -ba <specfile> ; rpmbuild -bb --target=i686 <specfile>.
> >
> > If anyone has got an idea.. :) Thanks for reading..