linux-kernel - Kernel 3.7.* Problerm

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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130120202003.46105e04704f19f219d6373e@gmail.com>
Date:	Sun, 20 Jan 2013 20:20:03 +0900
From:	Suho Park <suho.hrvatska@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Kernel 3.7.* Problerm

I used the following method since 2.4 version
1. copy .config from the old kernel
2. make oldconfig
(2-1. make dep)
3. make && make modules && make modules_install && make install
and then change the symbolic link of kernel header in /usr/include
to the compiled kernel header.
Works well from 2.4.0 up to 3.6.11

The problem is that 
3.6.11----->3.7.0 is OK
3.7.0 ----->3.7.1 not OK
3.7.1----->3.7.3 not OK

The point is that kerhel header is devided
into two parts linux/include/linux,
linux/include/uapi/linux.

The solution is that I always change the kernel
header includes to point 3.6.11, and compile 3.7.3

There are many applications using linux kernel header,
and I add the following in Makefile
-I/usr/include/uapi, where uapi is symbolically linked to
the kernel/include/uapi, for example I tested netfilter.

Is there any good reason of the division of the kernel headers?
Or is there any good solution?.

-- 
++++++++++++++++++++++++++
Suho Park(suhopark@...h.snu.ac.kr)
+82-10-3450-6216
++++++++++++++++++++++++++
--
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/