summaryrefslogtreecommitdiffstats
path: root/Makefile
AgeCommit message (Collapse)Author
2018-11-04Linux 4.14.79v4.14.79Greg Kroah-Hartman
2018-11-04kbuild: set no-integrated-as before incl. arch MakefileStefan Agner
[ Upstream commit 0f0e8de334c54c38818a4a5390a39aa09deff5bf ] In order to make sure compiler flag detection for ARM works correctly the no-integrated-as flags need to be set before including the arch specific Makefile. Fixes: cfe17c9bbe6a ("kbuild: move cc-option and cc-disable-warning after incl. arch Makefile") Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
2018-10-20Linux 4.14.78v4.14.78Greg Kroah-Hartman
2018-10-18Linux 4.14.77v4.14.77Greg Kroah-Hartman
2018-10-13Linux 4.14.76v4.14.76Greg Kroah-Hartman
2018-10-10Linux 4.14.75v4.14.75Greg Kroah-Hartman
2018-10-03Linux 4.14.74v4.14.74Greg Kroah-Hartman
2018-09-29Linux 4.14.73v4.14.73Greg Kroah-Hartman
2018-09-26Linux 4.14.72v4.14.72Greg Kroah-Hartman
2018-09-19Linux 4.14.71v4.14.71Greg Kroah-Hartman
2018-09-15Linux 4.14.70v4.14.70Greg Kroah-Hartman
2018-09-09Linux 4.14.69v4.14.69Greg Kroah-Hartman
2018-09-05Linux 4.14.68v4.14.68Greg Kroah-Hartman
2018-09-05x86/vdso: Fix vDSO build if a retpoline is emittedAndy Lutomirski
commit 2e549b2ee0e358bc758480e716b881f9cabedb6a upstream. Currently, if the vDSO ends up containing an indirect branch or call, GCC will emit the "external thunk" style of retpoline, and it will fail to link. Fix it by building the vDSO with inline retpoline thunks. I haven't seen any reports of this triggering on an unpatched kernel. Fixes: commit 76b043848fd2 ("x86/retpoline: Add initial retpoline support") Signed-off-by: Andy Lutomirski <luto@kernel.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Matt Rickard <matt@softrans.com.au> Cc: Borislav Petkov <bp@alien8.de> Cc: Jason Vas Dias <jason.vas.dias@gmail.com> Cc: David Woodhouse <dwmw2@infradead.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Andi Kleen <ak@linux.intel.com> Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/c76538cd3afbe19c6246c2d1715bc6a60bd63985.1534448381.git.luto@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-08-24Linux 4.14.67v4.14.67Greg Kroah-Hartman
2018-08-24kbuild: suppress warnings from 'getconf LFS_*'Masahiro Yamada
[ Upstream commit 6d79a7b424a5630a6fcab31fd7c38af4ea9c9a0f ] Suppress warnings for systems that do not recognize LFS_*. getconf: no such configuration parameter `LFS_CFLAGS' getconf: no such configuration parameter `LFS_LDFLAGS' getconf: no such configuration parameter `LFS_LIBS' Fixes: d7f14c66c273 ("kbuild: Enable Large File Support for hostprogs") Reported-by: Chen Feng <puck.chen@hisilicon.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-08-22Linux 4.14.66v4.14.66Greg Kroah-Hartman
2018-08-18Linux 4.14.65v4.14.65Greg Kroah-Hartman
2018-08-17Linux 4.14.64v4.14.64Greg Kroah-Hartman
2018-08-15Linux 4.14.63v4.14.63Greg Kroah-Hartman
2018-08-09Linux 4.14.62v4.14.62Greg Kroah-Hartman
2018-08-06Linux 4.14.61v4.14.61Greg Kroah-Hartman
2018-08-03Linux 4.14.60v4.14.60Greg Kroah-Hartman
2018-07-28Linux 4.14.59v4.14.59Greg Kroah-Hartman
2018-07-28turn off -Wattribute-aliasArnd Bergmann
Starting with gcc-8.1, we get a warning about all system call definitions, which use an alias between functions with incompatible prototypes, e.g.: In file included from ../mm/process_vm_access.c:19: ../include/linux/syscalls.h:211:18: warning: 'sys_process_vm_readv' alias between functions of incompatible types 'long int(pid_t, const struct iovec *, long unsigned int, const struct iovec *, long unsigned int, long unsigned int)' {aka 'long int(int, const struct iovec *, long unsigned int, const struct iovec *, long unsigned int, long unsigned int)'} and 'long int(long int, long int, long int, long int, long int, long int)' [-Wattribute-alias] asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \ ^~~ ../include/linux/syscalls.h:207:2: note: in expansion of macro '__SYSCALL_DEFINEx' __SYSCALL_DEFINEx(x, sname, __VA_ARGS__) ^~~~~~~~~~~~~~~~~ ../include/linux/syscalls.h:201:36: note: in expansion of macro 'SYSCALL_DEFINEx' #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__) ^~~~~~~~~~~~~~~ ../mm/process_vm_access.c:300:1: note: in expansion of macro 'SYSCALL_DEFINE6' SYSCALL_DEFINE6(process_vm_readv, pid_t, pid, const struct iovec __user *, lvec, ^~~~~~~~~~~~~~~ ../include/linux/syscalls.h:215:18: note: aliased declaration here asmlinkage long SyS##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \ ^~~ ../include/linux/syscalls.h:207:2: note: in expansion of macro '__SYSCALL_DEFINEx' __SYSCALL_DEFINEx(x, sname, __VA_ARGS__) ^~~~~~~~~~~~~~~~~ ../include/linux/syscalls.h:201:36: note: in expansion of macro 'SYSCALL_DEFINEx' #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__) ^~~~~~~~~~~~~~~ ../mm/process_vm_access.c:300:1: note: in expansion of macro 'SYSCALL_DEFINE6' SYSCALL_DEFINE6(process_vm_readv, pid_t, pid, const struct iovec __user *, lvec, This is really noisy and does not indicate a real problem. In the latest mainline kernel, this was addressed by commit bee20031772a ("disable -Wattribute-alias warning for SYSCALL_DEFINEx()"), which seems too invasive to backport. This takes a much simpler approach and just disables the warning across the kernel. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-07-25Linux 4.14.58v4.14.58Greg Kroah-Hartman
2018-07-22Linux 4.14.57v4.14.57Greg Kroah-Hartman
2018-07-17Linux 4.14.56v4.14.56Greg Kroah-Hartman
2018-07-11Linux 4.14.55v4.14.55Greg Kroah-Hartman
2018-07-08Linux 4.14.54v4.14.54Greg Kroah-Hartman
2018-07-03Linux 4.14.53v4.14.53Greg Kroah-Hartman
2018-06-26Linux 4.14.52v4.14.52Greg Kroah-Hartman
2018-06-21Linux 4.14.51v4.14.51Greg Kroah-Hartman
2018-06-16Linux 4.14.50v4.14.50Greg Kroah-Hartman
2018-06-11Linux 4.14.49v4.14.49Greg Kroah-Hartman
2018-06-05Linux 4.14.48v4.14.48Greg Kroah-Hartman
2018-06-05kbuild: clang: disable unused variable warnings only when constantSodagudi Prasad
commit 0a5f41767444cc3b4fc5573921ab914b4f78baaa upstream. Currently, GCC disables -Wunused-const-variable, but not -Wunused-variable, so warns unused variables if they are non-constant. While, Clang does not warn unused variables at all regardless of the const qualifier because -Wno-unused-const-variable is implied by the stronger option -Wno-unused-variable. Disable -Wunused-const-variable instead of -Wunused-variable so that GCC and Clang work in the same way. Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-06-05kbuild: clang: remove crufty HOSTCFLAGSNick Desaulniers
commit df16aaac26e92e97ab7234d3f93c953466adc4b5 upstream. When compiling with `make CC=clang HOSTCC=clang`, I was seeing warnings that clang did not recognize -fno-delete-null-pointer-checks for HOSTCC targets. These were added in commit 61163efae020 ("kbuild: LLVMLinux: Add Kbuild support for building kernel with Clang"). Clang does not support -fno-delete-null-pointer-checks, so adding it to HOSTCFLAGS if HOSTCC is clang does not make sense. It's not clear why the other warnings were disabled, and just for HOSTCFLAGS, but I can remove them, add -Werror to HOSTCFLAGS and compile with clang just fine. Suggested-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Nick Desaulniers <nick.desaulniers@gmail.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-05-30Linux 4.14.47v4.14.47Greg Kroah-Hartman
2018-05-30Linux 4.14.46v4.14.46Greg Kroah-Hartman
2018-05-30Linux 4.14.45v4.14.45Greg Kroah-Hartman
2018-05-25Linux 4.14.44v4.14.44Greg Kroah-Hartman
2018-05-22Linux 4.14.43v4.14.43Greg Kroah-Hartman
2018-05-19Linux 4.14.42v4.14.42Greg Kroah-Hartman
2018-05-16Linux 4.14.41v4.14.41Greg Kroah-Hartman
2018-05-09Linux 4.14.40v4.14.40Greg Kroah-Hartman
2018-05-01Linux 4.14.39v4.14.39Greg Kroah-Hartman
2018-04-29Linux 4.14.38v4.14.38Greg Kroah-Hartman
2018-04-26Linux 4.14.37v4.14.37Greg Kroah-Hartman
2018-04-24Linux 4.14.36v4.14.36Greg Kroah-Hartman