Bug 184205 - kernel modules strip trick?
Summary: kernel modules strip trick?
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-07 07:43 UTC by Robinson Tiemuqinke
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-07 16:01:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Robinson Tiemuqinke 2006-03-07 07:43:45 UTC
Description of problem:

 FC4 default stock kernel has a no more than 
100MB /usr/lib/<redhat_kernel_modules>/ directory even it has almost all 
options selected in module form. While a compilation of kernel 2.6.15 kernel 
has a much bigger (>200MB) /usr/lib/<custom_kernel_modules>/ directory when 
has only about 1/3 options selected. Both kernels have the same kernel(debug) 
hack settings.

 The default Makefile for 2.6.* kernel doesn't have a "make strip" option, how 
the redhat kernel stripped the kernel modules?


Version-Release number of selected component (if applicable):

kernel-2.6.15-1.1831_FC4
kernel-2.6.15-1.1831_FC4smp


How reproducible:

Every time.

Steps to Reproduce:
1. just recompile FC4 stock kernel and then build and install it; 

2. download a vanilla 2.6 kernel from www.kernel.org, run "make config; make; 
make modules_install install". There doesn't have a "make stripInstall" option.

3. You will see that the vanilla kernels module directory is much bigger than 
FC4 kernel, the vmlinuz under /boot shows the same symptom.

Actual results:

[root@testnode01 modules]# ls -alF /boot/vmlinuz-2*
-rw-r--r--  1 root root 1811801 Feb  7 10:47 /boot/vmlinuz-2.6.15-1.1831_FC4
-rw-r--r--  1 root root 1811805 Feb  7 11:01 /boot/vmlinuz-2.6.15-1.1831_FC4smp
-rw-r--r--  1 root root 2794641 Mar  6 22:19 /boot/vmlinuz-2.6.15-6_64GB

[root@testnode01 modules]# du -sk /lib/modules/*
95676   2.6.15-1.1831_FC4
95696   2.6.15-1.1831_FC4smp
219620  2.6.15-6_64GB

[root@testnode01 /]# find /usr/lib/2.6.15-6_64GB/ -type f -name '*.ko' | xargs 
strip
[root@testnode01 /]# du -sk /usr/lib/2.6.15-6_64GB/
32932   /usr/lib/2.6.15-6_64GB/

[root@testnode01 linux-2.6.15.6]# strip /boot/vmlinuz-2.6.15-6_64GB
strip: /boot/vmlinuz-2.6.15-6_64GB: File format not recognized



Expected results:


Additional info:

It is not strictly a bug, just wonder how redhat does the trick to 
strip|shrink size of vmlinuz and kernel modules.

Comment 1 Warren Togami 2006-03-07 16:01:33 UTC
NOTABUG, this is simply how binary RPMS are built.

See scripts like /usr/lib/rpm/brp-strip included in the rpm-build package.  It
strips the installed binaries and puts the original into *-debuginfo packages
purposes.


Note You need to log in before you can comment on or make changes to this bug.