summaryrefslogtreecommitdiff
path: root/Makefile
AgeCommit message (Collapse)Author
2018-02-16Linux 4.4.116v4.4.116Greg Kroah-Hartman
2018-02-03Linux 4.4.115v4.4.115Greg Kroah-Hartman
2018-01-31Linux 4.4.114v4.4.114Greg Kroah-Hartman
2018-01-23Linux 4.4.113v4.4.113Greg Kroah-Hartman
2018-01-17Linux 4.4.112v4.4.112Greg Kroah-Hartman
2018-01-10Linux 4.4.111v4.4.111Greg Kroah-Hartman
2018-01-05Linux 4.4.110v4.4.110Greg Kroah-Hartman
2018-01-02Linux 4.4.109v4.4.109Greg Kroah-Hartman
2018-01-02kbuild: add '-fno-stack-check' to kernel build optionsLinus Torvalds
commit 3ce120b16cc548472f80cf8644f90eda958cf1b6 upstream. It appears that hardened gentoo enables "-fstack-check" by default for gcc. That doesn't work _at_all_ for the kernel, because the kernel stack doesn't act like a user stack at all: it's much smaller, and it doesn't auto-expand on use. So the extra "probe one page below the stack" code generated by -fstack-check just breaks the kernel in horrible ways, causing infinite double faults etc. [ I have to say, that the particular code gcc generates looks very stupid even for user space where it works, but that's a separate issue. ] Reported-and-tested-by: Alexander Tsoy <alexander@tsoy.me> Reported-and-tested-by: Toralf Förster <toralf.foerster@gmx.de> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Jiri Kosina <jikos@kernel.org> Cc: Andy Lutomirski <luto@amacapital.net> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-12-25Linux 4.4.108v4.4.108Greg Kroah-Hartman
2017-12-20Linux 4.4.107v4.4.107Greg Kroah-Hartman
2017-12-16Linux 4.4.106v4.4.106Greg Kroah-Hartman
2017-12-09Linux 4.4.105v4.4.105Greg Kroah-Hartman
2017-12-05Linux 4.4.104v4.4.104Greg Kroah-Hartman
2017-11-30Linux 4.4.103v4.4.103Greg Kroah-Hartman
2017-11-24Linux 4.4.102v4.4.102Greg Kroah-Hartman
2017-11-24Linux 4.4.101v4.4.101Greg Kroah-Hartman
2017-11-21Linux 4.4.100v4.4.100Greg Kroah-Hartman
2017-11-18Linux 4.4.99v4.4.99Greg Kroah-Hartman
2017-11-15Linux 4.4.98v4.4.98Greg Kroah-Hartman
2017-11-08Linux 4.4.97v4.4.97Greg Kroah-Hartman
2017-11-02Linux 4.4.96v4.4.96Greg Kroah-Hartman
2017-10-27Linux 4.4.95v4.4.95Greg Kroah-Hartman
2017-10-21Linux 4.4.94v4.4.94Greg Kroah-Hartman
2017-10-18Linux 4.4.93v4.4.93Greg Kroah-Hartman
2017-10-12Linux 4.4.92v4.4.92Greg Kroah-Hartman
2017-10-08Linux 4.4.91v4.4.91Greg Kroah-Hartman
2017-10-05Linux 4.4.90v4.4.90Greg Kroah-Hartman
2017-09-27Linux 4.4.89v4.4.89Greg Kroah-Hartman
2017-09-13Linux 4.4.88v4.4.88Greg Kroah-Hartman
2017-09-07Linux 4.4.87v4.4.87Greg Kroah-Hartman
2017-09-02Linux 4.4.86v4.4.86Greg Kroah-Hartman
2017-08-30Linux 4.4.85v4.4.85Greg Kroah-Hartman
2017-08-24Linux 4.4.84v4.4.84Greg Kroah-Hartman
2017-08-16Linux 4.4.83v4.4.83Greg Kroah-Hartman
2017-08-12Linux 4.4.82v4.4.82Greg Kroah-Hartman
2017-08-11Linux 4.4.81v4.4.81Greg Kroah-Hartman
2017-08-06Linux 4.4.80v4.4.80Greg Kroah-Hartman
2017-07-27Linux 4.4.79v4.4.79Greg Kroah-Hartman
2017-07-27disable new gcc-7.1.1 warnings for nowLinus Torvalds
commit bd664f6b3e376a8ef4990f87d08271cc2d01ba9a upstream. I made the mistake of upgrading my desktop to the new Fedora 26 that comes with gcc-7.1.1. There's nothing wrong per se that I've noticed, but I now have 1500 lines of warnings, mostly from the new format-truncation warning triggering all over the tree. We use 'snprintf()' and friends in a lot of places, and often know that the numbers are fairly small (ie a controller index or similar), but gcc doesn't know that, and sees an 'int', and thinks that it could be some huge number. And then complains when our buffers are not able to fit the name for the ten millionth controller. These warnings aren't necessarily bad per se, and we probably want to look through them subsystem by subsystem, but at least during the merge window they just mean that I can't even see if somebody is introducing any *real* problems when I pull. So warnings disabled for now. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-07-21Linux 4.4.78v4.4.78Greg Kroah-Hartman
2017-07-15Linux 4.4.77v4.4.77Greg Kroah-Hartman
2017-07-05Linux 4.4.76v4.4.76Greg Kroah-Hartman
2017-07-05jump label: fix passing kbuild_cflags when checking for asm goto supportGleb Fotengauer-Malinovskiy
commit 7292ae3d5a18fb922be496e6bb687647193569b4 upstream. The latest change of asm goto support check added passing of KBUILD_CFLAGS to compiler. When these flags reference gcc plugins that are not built yet, the check fails. When one runs "make bzImage" followed by "make modules", the kernel is always built with HAVE_JUMP_LABEL disabled, while the modules are built depending on CONFIG_JUMP_LABEL. If HAVE_JUMP_LABEL macro happens to be different, modules are built with undefined references, e.g.: ERROR: "static_key_slow_inc" [net/netfilter/xt_TEE.ko] undefined! ERROR: "static_key_slow_dec" [net/netfilter/xt_TEE.ko] undefined! ERROR: "static_key_slow_dec" [net/netfilter/nft_meta.ko] undefined! ERROR: "static_key_slow_inc" [net/netfilter/nft_meta.ko] undefined! ERROR: "nf_hooks_needed" [net/netfilter/ipvs/ip_vs.ko] undefined! ERROR: "nf_hooks_needed" [net/ipv6/ipv6.ko] undefined! ERROR: "static_key_count" [net/ipv6/ipv6.ko] undefined! ERROR: "static_key_slow_inc" [net/ipv6/ipv6.ko] undefined! This change moves the check before all these references are added to KBUILD_CFLAGS. This is correct because subsequent KBUILD_CFLAGS modifications are not relevant to this check. Reported-by: Anton V. Boyarshinov <boyarsh@altlinux.org> Fixes: 35f860f9ba6a ("jump label: pass kbuild_cflags when checking for asm goto support") Signed-off-by: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Acked-by: David Lin <dtwlin@google.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-06-29Linux 4.4.75v4.4.75Greg Kroah-Hartman
2017-06-26Linux 4.4.74v4.4.74Greg Kroah-Hartman
2017-06-17Linux 4.4.73v4.4.73Greg Kroah-Hartman
2017-06-17jump label: pass kbuild_cflags when checking for asm goto supportDavid Lin
[ Upstream commit 35f860f9ba6aac56cc38e8b18916d833a83f1157 ] Some versions of ARM GCC compiler such as Android toolchain throws in a '-fpic' flag by default. This causes the gcc-goto check script to fail although some config would have '-fno-pic' flag in the KBUILD_CFLAGS. This patch passes the KBUILD_CFLAGS to the check script so that the script does not rely on the default config from different compilers. Link: http://lkml.kernel.org/r/20170120234329.78868-1-dtwlin@google.com Signed-off-by: David Lin <dtwlin@google.com> Acked-by: Steven Rostedt <rostedt@goodmis.org> Cc: Michal Marek <mmarek@suse.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-06-14Linux 4.4.72v4.4.72Greg Kroah-Hartman
2017-06-07Linux 4.4.71v4.4.71Greg Kroah-Hartman
generated by cgit v1.2.3 (git 2.0.4) at 2024-05-25 03:29:28 +0000