On Tue, Jul 31, 2018 at 12:45 PM, Patrick J. LoPresti

<[log in to unmask]> wrote:

> On Thu, Jul 26, 2018 at 6:57 AM Pat Riehecky <[log in to unmask]> wrote:

>>

>> On 07/26/2018 12:06 AM, Akemi Yagi wrote:

>> > On Wed, Jul 25, 2018 at 5:21 PM, Patrick J. LoPresti <[log in to unmask]> wrote:

>> >> As far as I can tell, the latest kmod-kvdo package for SL7.5 is

>> >> version 6.1.0-171-17.el7_5:

>> >>

>> >>    $ rpm -q --requires -p

>> >> ./x86_64/updates/fastbugs/kmod-kvdo-6.1.0.171-17.el7_5.x86_64.rpm |

>> >> grep dm_get_device

>> >>    kernel(dm_get_device) = 0xf3d46cd5

>> >>

>> >> ...while the latest kernel package is version 3.10.0-862-6.3.el7:

>> >>

>> >>    $ rpm -q --provides -p

>> >> ./x86_64/updates/security/kernel-3.10.0-862.6.3.el7.x86_64.rpm | grep

>> >> dm_get_device

>> >>    kernel(dm_get_device) = 0x602cd186

>> >>

>> >> As you can see from the requires/provides, these packages are

>> >> incompatible. (A few other dm_xxx symbols are similarly mismatched.)

>> >>

>> >> Note that the next-to-latest kernel, 3.10.0-862.3.3, provides the

>> >> symbol versions that the latest kmod-kvdo is expecting. So it appears

>> >> that kmod-kvdo is out of date (?)

>> >>

>> >>   - Pat

>> > Good catch.

>> >

>> > It looks like kmod-kvdo-6.1.0.171-17.el7_5 was built against

>> > kernel-3.10.0-862.el7. It needs to be rebuilt against the

>> > 3.10.0-862.6.1.el7 kernel to match the upstream (RH) package. It will

>> > then work with the newer 7.5 kernels as well.

>> >

>> > Akemi

>>

>> I'll get a rebuild scheduled against the newer kernel.

>>

>> Pat

>

> The just-released kmod-kvdo-6.1.0.171-17.el7_5.0.x86_64.rpm and

> ./x86_64/updates/fastbugs/kernel-3.10.0-862.9.1.el7.x86_64.rpm appear

> to have the exact same issue.

>

>  - Pat



Pat (of SL :)



It is still built against kernel-3.10.0-862.el7. Could you try again

and make sure the kmod is built against 3.10.0-862.6.1.el7

(which is what the upstream package used)?



Akemi