On Mar 6, 2008, at 7:34 PM, Ed Brown wrote:

> Jarod Wilson wrote:
>> Best way to learn is by finding one already out in the wild and
>> modifying it to your own kernel module.
>
> I'm chipping away at this... Got an rpm to build, but it fails to
> install with:
>
> # rpm -Uvh kmod-myri10ge-1.4.1-1.x86_64.rpm
> error: Failed dependencies:
>     ksym(mtrr_del) = 272d394e is needed by kmod-
> myri10ge-1.4.1-1.x86_64
>     ksym(mtrr_add) = 56179c5f is needed by kmod-
> myri10ge-1.4.1-1.x86_64
>
> Rpm's '--what-provides' doesn't provide a clue here: any ideas
> what's missing?

The kmod requires the kernel symbols mtrr_del and mtrr_add, which I'd
wager a guess aren't in the kabi whitelist, and thus not "provided" by
any installed kernel.

Okay, just double-checked... mtrr_add and mtrr_del are on the kabi
whitelist for i686, but not for x86_64. So yeah, those symbols aren't
whitelisted for x86_64, so the x86_64 kernel doesn't Provide them for
you.


> Also, I'm trying to understand exactly what the kmod packaging
> provides. I've read Jon Masters presentation here:
> <http://people.redhat.com/jcm/talks/jcm_rhsummit_07.pdf>, but still
> not clear on just how far a kernel module packaged this way will go.
> I assume kernel upgrades that don't change the ABI symbol dependencies
> won't require a new kernel module rpm, but how can I know before
> upgrading a kernel when it will require a new module rpm as well?

Not sure exactly. But for stuff that's whitelisted, Red Hat has
committed to *never* upgrading the kernel in a way that breaks the ABI
for whitelisted symbols (unless absolutely required for a security bug
that can't be fixed without breaking the ABI).

--
Jarod Wilson
jwilson@(protected)


_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list