<div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 8, 2019 at 6:07 PM Akemi Yagi <<a href="mailto:amyagi@gmail.com">amyagi@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Sep 25, 2019 at 12:53 PM Andrew Walsh <<a href="mailto:awalsh@redhat.com" target="_blank">awalsh@redhat.com</a>> wrote:<br>
><br>
> On Wed, Sep 25, 2019 at 3:47 PM Brian Stinson <<a href="mailto:brian@bstinson.com" target="_blank">brian@bstinson.com</a>> wrote:<br>
> ><br>
> > On Wed, Sep 25, 2019, at 14:39, Andrew Walsh wrote:<br>
> > > Hello,<br>
> > ><br>
> > > First, let me express how excited I am by the news of the CentOS<br>
> > > Stream offering. I am really looking forward to how this works out in<br>
> > > the long run.<br>
> > ><br>
> > > I am in the group that builds VDO, and it is currently delivered as a<br>
> > > kmod in CentOS Stream, RHEL, and CentOS. This requires that if the<br>
> > > signatures of the symbols that VDO uses change from one kernel to the<br>
> > > next, we may need to rebuild the package against the more recent<br>
> > > kernel.<br>
> > ><br>
> > > The current version of kmod-kvdo (6.2.0.293-50.el8) delivered in<br>
> > > CentOS Stream is the equivalent of the RHEL-8.0/CentOS-8.0 GA, while<br>
> > > the version of the kernel (4.18.0-144.el8) is newer. In the time<br>
> > > between the kernel that kmod-kvdo was built against (4.18.0-72.el8)<br>
> > > and the current kernel in CentOS Stream, the signatures have changed.<br>
> > > As a result, the kernel modules delivered in the kmod-kvdo package<br>
> > > cannot be loaded due to symbol mismatches (all device mapper related<br>
> > > symbols that change periodically, from what I've experienced).<br>
> > ><br>
> > > I believe that a simple rebuild of kmod-kvdo-6.2.0.293-50.el8 against<br>
> > > kernel-4.18.0-144.el8 should be effective enough to get it working<br>
> > > again.<br>
> > ><br>
> > > How can I help facilitate this rebuild now and/or moving forward? I<br>
> > > realize that things are still very much in motion and not fully<br>
> > > implemented/decided at this point.<br>
> > ><br>
> > > Andy Walsh<br>
<br>
> It would actually happen from<br>
> <a href="https://git.centos.org/rpms/kmod-kvdo/tree/c8" rel="noreferrer" target="_blank">https://git.centos.org/rpms/kmod-kvdo/tree/c8</a> since the vdo package<br>
> just provides the user space libraries and utilities.<br>
><br>
> ><br>
> > or are there changes needed?<br>
><br>
> The only changes that should be needed (though I haven't tested it to<br>
> be 100% certain), is to update the required kernel to make sure it<br>
> builds against the proper kernel and also bump the Release field in<br>
> the spec from 53 to 54 to get a new NVR.<br>
><br>
> Change line 4<br>
> %define spec_release 53<br>
> To:<br>
> %define spec_release 54<br>
><br>
><br>
> Change line 9<br>
> %define kmod_kernel_version 4.18.0-80.10.1.el8_0<br>
> To:<br>
> %define kmod_kernel_version 4.18.0-144.el8<br>
<br>
> Andy Walsh<br>
<br>
kmod-kvdo is in the BaseOS repo, so I'd think the version for CentOS<br>
Stream should be published in the Stream-BaseOS repo.<br>
<br>
By the way I built kmod-kvdo against the -144 kernel and it (modprobe<br>
kvdo) seems to work. Whether this weak-links against the next kernel<br>
update remains to be seen. </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Akemi<br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a></blockquote><div><br></div><div><br></div><div>Hello,</div><div><br></div><div>Just following up on this thread. kmod-kvdo-6.2.0.293-53.el8_0 is available in the CentOS Stream repos, and I've just confirmed that it works on the kernel-4.18.0-144.el8 kernel.</div><div><br></div><div>Please let me know if anyone experiences otherwise.</div><div><br></div><div>Thanks,</div><div>-Andy </div></div></div>