user/sven/linux.git/Makefile, branch v4.14.157Linux Kernel
https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.14.1572019-12-01T08:14:37ZLinux 4.14.1572019-12-01T08:14:37ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-12-01T08:14:37Zurn:sha1:fbc5fe7a54d02e11972e3b2a5ddb6ffc88162c8fLinux 4.14.1562019-11-24T07:23:35ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-11-24T07:23:35Zurn:sha1:43598c571e7ed29e4c81e35b4a870fe6b9f8d58eLinux 4.14.1552019-11-20T17:00:54ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-11-20T17:00:54Zurn:sha1:f56f3d0e65adb447b8b583c8ed4fbbe544c9bfdeLinux 4.14.1542019-11-12T18:19:08ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-11-12T18:19:08Zurn:sha1:775d01b65b5daa002a9ba60f2d2bb3b1a6ce12fbLinux 4.14.1532019-11-10T10:25:43ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-11-10T10:25:43Zurn:sha1:4762bcd451a9e92e79d5146d3d4a5ffe2b4e0ec5kbuild: add -fcf-protection=none when using retpoline flags2019-11-10T10:25:39ZSeth Forsheeseth.forshee@canonical.com2019-07-17T16:06:26Zurn:sha1:2103cc67dbfbcfc5c5838d4d0859631e9f3dfce3
[ Upstream commit 29be86d7f9cb18df4123f309ac7857570513e8bc ]
The gcc -fcf-protection=branch option is not compatible with
-mindirect-branch=thunk-extern. The latter is used when
CONFIG_RETPOLINE is selected, and this will fail to build with
a gcc which has -fcf-protection=branch enabled by default. Adding
-fcf-protection=none when building with retpoline enabled
prevents such build failures.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
kbuild: use -fmacro-prefix-map to make __FILE__ a relative path2019-11-10T10:25:38ZMasahiro Yamadayamada.masahiro@socionext.com2018-03-30T04:15:26Zurn:sha1:b125188db9b12a3d6f7fc7d3a66929f2ffae7872
[ Upstream commit a73619a845d5625079cc1b3b820f44c899618388 ]
The __FILE__ macro is used everywhere in the kernel to locate the file
printing the log message, such as WARN_ON(), etc. If the kernel is
built out of tree, this can be a long absolute path, like this:
WARNING: CPU: 1 PID: 1 at /path/to/build/directory/arch/arm64/kernel/foo.c:...
This is because Kbuild runs in the objtree instead of the srctree,
then __FILE__ is expanded to a file path prefixed with $(srctree)/.
Commit 9da0763bdd82 ("kbuild: Use relative path when building in a
subdir of the source tree") improved this to some extent; $(srctree)
becomes ".." if the objtree is a child of the srctree.
For other cases of out-of-tree build, __FILE__ is still the absolute
path. It also means the kernel image depends on where it was built.
A brand-new option from GCC, -fmacro-prefix-map, solves this problem.
If your compiler supports it, __FILE__ is the relative path from the
srctree regardless of O= option. This provides more readable log and
more reproducible builds.
Please note __FILE__ is always an absolute path for external modules.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Linux 4.14.1522019-11-06T11:43:42ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-11-06T11:43:42Zurn:sha1:c9fda4f22428e09728b611ec9100157199039bfeLinux 4.14.1512019-10-29T08:17:49ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-10-29T08:17:49Zurn:sha1:ddef1e8e3f6eb26034833b7255e3fa584d54a230Linux 4.14.1502019-10-17T20:44:04ZGreg Kroah-Hartmangregkh@linuxfoundation.org2019-10-17T20:44:04Zurn:sha1:b98aebd298246df37b472c52a2ee1023256d02e3