On Tue, May 26, 2009 at 1:51 PM, Tru Huynh tru@centos.org wrote:
On Tue, May 26, 2009 at 08:16:42AM -0700, Akemi Yagi wrote:
Here is the updated version:
http://centos.toracat.org/kmods/CentOS-4/xfs/SRPMS/
Please discard the obsoleted ones (I did not bump the version/release number). Let me know when your binaries are ready for testing.
rebuilds and uploaded.
* Downloaded from http://people.centos.org/tru/kABI/4/RPMS/ and did some test installs.
First, installed the kernel version specific kmod-xfs-0.4-1.el4.2.6.9_78.0.22 to the test box and then installed the current kABI-tracking kmod-xfs-0.4-2.el4. It successfully replaced the xfs.ko installed by the former and created symlinks to other installed kernels correctly.
Second, installed the current kmod-xfs to an older kernel and then updated the kernel. Upon reboot, a new symlink was created for the newly installed kernel successfully.
Third, confirmed that the kABI-tracking kmod-xfs recognized centosplus kernels as expected (even -vm kernels). One example of such symlinks:
$ uname -mr 2.6.9-78.0.22.plus.c4 i686
$ ls -l `find /lib/modules -name xfs.ko` lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-67.0.1.EL.plus.c4/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-67.0.22.ELvm/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-67.0.4.plus.c4/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-78.0.1.ELvm/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-78.0.1.plus.c4/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko -rw-r--r-- 1 root root 598576 May 26 13:07 /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:34 /lib/modules/2.6.9-78.0.22.plus.c4/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-78.0.5.EL/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-78.0.5.plus.c4/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-78.0.8.plus.c4/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko lrwxrwxrwx 1 root root 46 May 26 18:20 /lib/modules/2.6.9-78.plus.c4/weak-updates/xfs/xfs.ko -> /lib/modules/2.6.9-78.0.22.EL/extra/xfs/xfs.ko
* I can only test installs/uninstalls. If someone can test it by actually *using* it, that will be great. I did not touch the code, so it should work. Nevertheless...
* Some side note
In the current kmod-xfs, modules are partially strip'ed. This has a dramatic effect on the size of the modules (hence the packages themselves). For example, the obsoleted rpm's were this big:
3413556 May 25 16:50 kmod-xfs-0.4-2.el4.i686.rpm 3500186 May 25 16:50 kmod-xfs-0.4-2.el4.x86_64.rpm
The current packages are:
299042 May 26 13:23 kmod-xfs-0.4-2.el4.i686.rpm 308712 May 26 13:23 kmod-xfs-0.4-2.el4.x86_64.rpm
All in-kernel modules are strip'ed during compilation. While it is not required, I think it's better to process the kmods the same way.
Akemi
On Wed, May 27, 2009 at 8:24 AM, Akemi Yagiamyagi@gmail.com wrote:
On Tue, May 26, 2009 at 1:51 PM, Tru Huynh tru@centos.org wrote:
On Tue, May 26, 2009 at 08:16:42AM -0700, Akemi Yagi wrote:
Here is the updated version:
http://centos.toracat.org/kmods/CentOS-4/xfs/SRPMS/
Please discard the obsoleted ones (I did not bump the version/release number). Let me know when your binaries are ready for testing.
rebuilds and uploaded.
- Downloaded from http://people.centos.org/tru/kABI/4/RPMS/ and did
some test installs.
First, installed the kernel version specific kmod-xfs-0.4-1.el4.2.6.9_78.0.22 to the test box and then installed the current kABI-tracking kmod-xfs-0.4-2.el4. It successfully replaced the xfs.ko installed by the former and created symlinks to other installed kernels correctly.
Second, installed the current kmod-xfs to an older kernel and then updated the kernel. Upon reboot, a new symlink was created for the newly installed kernel successfully.
Third, confirmed that the kABI-tracking kmod-xfs recognized centosplus kernels as expected (even -vm kernels). One example of such symlinks:
Tru,
I vaguely remember that you were planning on releasing this on or around June 15 (?). Maybe it's time? I don't think we are getting any more response here.
Akemi
On Mon, Jun 15, 2009 at 12:08:30AM -0700, Akemi Yagi wrote:
Tru,
Hi Akemi,
I vaguely remember that you were planning on releasing this on or around June 15 (?). Maybe it's time? I don't think we are getting any more response here.
All the CentOS-4 kmod-xfs have now been promoted to the extras/centosplus repositories.
Cheers,
Tru
Tru Huynh wrote:
I vaguely remember that you were planning on releasing this on or around June 15 (?). Maybe it's time? I don't think we are getting any more response here.
All the CentOS-4 kmod-xfs have now been promoted to the extras/centosplus repositories.
To call these packages kABI tracking is misleading. They are kernel version independent but they don't track the kABI like the el5 packages do. Notice the difference below.
[root@server 4.7]# rpm -qp --requires kmod-xfs-0.4-2.el4.i686.rpm rpmlib(VersionedDependencies) <= 3.0.3-1 /sbin/depmod /sbin/depmod module-init-tools >= 3.1-0.pre5.3.10 /bin/sh /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1
[root@server 5.3]# rpm -qp --requires kmod-xfs-0.4-2.i686.rpm rpmlib(VersionedDependencies) <= 3.0.3-1 /sbin/depmod /sbin/depmod /bin/sh /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 kernel(rhel5_fs_ga) = b96eba087460900b3aa6064930cf23d58908d4d6 kernel(rhel5_mm_ga) = 09f63dfab81bba7e01a2bf693f5ce125db466051 kernel(rhel5_vmlinux_ga) = 2bf444396ff7060828059d7a5379435140aee48a kernel(rhel5_kernel_ga) = 2cd142708e2d573b2de522df5df87aaeb7c1d298 kernel(rhel5_lib_ga) = 088a6b77cde4f82c65b0d7f34802cfa41d209328 kernel(rhel5_kernel_module_ga) = 1b051ce57d6b18fdf071786f6f7296d3d0ab28f9 kernel(rhel5_block_ga) = a42055e630b73ddd7254fc6963814e16913852e5 kernel(rhel5_init_ga) = e18da0926c862eaed98f20f312403ea33c944cbd kernel(rhel5_kernel_power_ga) = 3c2c37d553ebecf99e6d147387f3dd4b5f5df7b7 kernel(rhel5_fs_proc_ga) = 6c027eb4cc65e0d557f1148fdba87f41cff17d2c kernel(rhel5_drivers_xen_core_ga) = 5308a7766723999bbea99a33dde1bbb76fee41ca kernel(rhel5_arch_i386_kernel_ga) = d1c30e0a553e9225eebd1b866e0d3ed7a6154147 kernel(rhel5_arch_i386_mm_ga) = 0164a9bd3f1d0935cd3dcb734785179f25c1a064 kernel(rhel5_fs_partitions_ga) = 1fab1cfd92c6a68656412e03aa5c2d03adac0971 kernel(rhel5_security_ga) = f89a464b3af98aaee0f0fda10a8ea9bfc9d0ae99
On Wed, Jun 17, 2009 at 2:54 PM, Shad L. Lords slords@lordsfam.net wrote:
All the CentOS-4 kmod-xfs have now been promoted to the extras/centosplus repositories.
To call these packages kABI tracking is misleading. They are kernel version independent but they don't track the kABI like the el5 packages do. Notice the difference below.
[root@server 4.7]# rpm -qp --requires kmod-xfs-0.4-2.el4.i686.rpm rpmlib(VersionedDependencies) <= 3.0.3-1 /sbin/depmod /sbin/depmod module-init-tools >= 3.1-0.pre5.3.10 /bin/sh /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1
[root@server 5.3]# rpm -qp --requires kmod-xfs-0.4-2.i686.rpm rpmlib(VersionedDependencies) <= 3.0.3-1 /sbin/depmod /sbin/depmod /bin/sh /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 kernel(rhel5_fs_ga) = b96eba087460900b3aa6064930cf23d58908d4d6
(snip)
The concept of "kABI-tracking" may be still new in CentOS-4 and is not mature IIHO. Unlike CentOS-5, CentOS-4 does not offer a full set of RPM packaging macros and the kernels do not have kABI meta information. Therefore, CentOS-4 kmods will not have kernel symbols as you showed above.
The weak-modules script was implemented in CentOS-4.7 by backporting from CentOS-5. It obtains modversions from a module and uses it to determine whether the module is kABI compatible with the kernel it is checking against.
So, whether or not this whole process in CentOS-4 can be called "kABI-tracking" may be debatable. Personally, if a module is kernel-independent and installs correctly only in compatible kernels, it is tracking the kABI. But that may or may not be so depending on how you look at it.
Akemi
-
Akemi Yagi -
Shad L. Lords -
Tru Huynh