| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 18 Sep 2014 07:34:49 -0400 From: r02@...e-mail.net To: linux-kernel@...r.kernel.org Subject: kernel version problem after patching There is a kernel version problem after patching the kernel. After installing the kernel and the kernel modules, without patching the kernel, then "uname" shows the right kernel version and in "/lib/modules/" there was the right directory created. But after patching the kernel, installing it and the modules, then the kernelversion shown with "uname" and the modules directory in "/lib/modules/" is not correct anymore. For example: If i download the kernel 3.14.19, patch it, and install the kernel and the modules then "uname" shows kernel version 3.14.0 and the modules are installed in "/lib/modules/3.14.0/" instead of 3.14.19 which would be the correct version. The same problem happens with other kernel versions too below 3.14.19 and also to kernel version 3.16.3 and versions below. But probably much more kernel versions are affected from this problem. If someone has an older kernel installed correctly, 3.16 for example, and wants to install a patched second kernel, 3.16.3 for example, then the modules directory of the first one will be overwritten unwanted due to this version error because both kernels have the same modules directory "/lib/modules/3.16.0". -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists