dkms and corruption of kernel-devel package

[Panu Matilainen]

On 08/21/2012 07:49 PM, Andre Robatino wrote:
> I've noticed that immediately after installing the kernel-devel package, the
> mtimes on many of its files fail verification, for example
>
> [root at compaq-pc ~]# rpm -V kernel-devel-3.5.2-1.fc17.x86_64
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/Kconfig
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/Kconfig
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/Kconfig
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/Kconfig.debug
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/Makefile
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/boot/Makefile
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/kernel/Makefile
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/lib/Makefile
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/math-emu/Makefile
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/mm/Makefile
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/oprofile/Makefile
> .......T.    /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/arm/Kconfig
>
> and so on. This happens even on old kernels (< 3.5.0) and whether or not dkms is
> installed. On kernels >= 3.5.0, with dkms installed, I also noticed that after
> installing VirtualBox guest additions for either the host or the guest, the
> corresponding /usr/src/kernels/*/System.map file belonging to kernel-devel is
> missing. I filed https://www.virtualbox.org/ticket/10847 . My questions are, is
> it normal for the files in kernel-devel to fail mtime verification immediately
> after install, and does anyone have any idea what's going on with the missing
> System.map? One of the vbox developers is of the opinion that it's not a vbox
> bug (see https://www.virtualbox.org/ticket/10709#comment:12 ) and that may well
> be true, but if so, which Fedora component is likely responsible? kernel? dkms?

Dunno about the System.map (other than I've always relied on the ones in 
/boot), but as for the timestamps, kernel-devel itself causes that as it 
runs hardlink on itself at package post-installation.

	- Panu -