linux-kernel - Re: kernel version problem after patching

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <trinity-253b1e32-44e3-400a-82b3-1c78f5446adf-1412776709482@3capp-1and1-bs01>
Date:	Wed, 8 Oct 2014 15:58:29 +0200
From:	e40@...ine.de
To:	linux-kernel@...r.kernel.org
Subject: Re: kernel version problem after patching

  
To solve this error you have to edit the "Makefile" inside the 
main kernel directory after you have patched the kernel.

At the beginning of the "Makefile" there are three variables
which can contain wrong values after patching. These are:
"PATCHLEVEL", "SUBLEVEL" and "EXTRAVERSION".

 ---

On Thursday 18 September 2014, r02@...e-mail.net wrote:
>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/