Subject: Re: LKM kernel version mismatch
To: Andrew Brown <firstname.lastname@example.org>
From: Love <email@example.com>
Date: 12/01/2003 15:09:45
Andrew Brown <firstname.lastname@example.org> writes:
>>> is there any easy way of disabling it? or making an lkm that will
>>> load more "easily"?
>>How do you determine what's 'safe' and what not? Once you
>>dereference any kernel struct pointer (e.g. struct proc or struct lwp),
>>there is incompatibility. Obviously it's not possible for a LKM
>>to do anything useful and be ABI safe.
> i'll buy that, but i'm not *doing* any of that. at all. that's my
> point. i can completely pigeonhole the api that i'm using.
> maybe i'll just make my own kernel option to disable the check...
So when struct sysent change, you will fall over...
I think you are complaning about the wrong thing. The problem I see is that
the version number is not related (well maybe, is it) to the kernel ABI for
release branches, while its most certainly is for current/HEAD.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----