linux-stable.git - Linux kernel stable tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	Linux 3.18.100v3.18.100	Greg Kroah-Hartman	2018-03-18	1	-1/+1
\|
*	Linux 3.18.99v3.18.99	Greg Kroah-Hartman	2018-03-11	1	-1/+1
\|
*	Linux 3.18.98v3.18.98	Greg Kroah-Hartman	2018-03-03	1	-1/+1
\|
*	Linux 3.18.97v3.18.97	Greg Kroah-Hartman	2018-02-28	1	-1/+1
\|
*	Linux 3.18.96v3.18.96	Greg Kroah-Hartman	2018-02-25	1	-1/+1
\|
*	Linux 3.18.95v3.18.95	Greg Kroah-Hartman	2018-02-16	1	-1/+1
\|
*	Linux 3.18.94v3.18.94	Greg Kroah-Hartman	2018-02-07	1	-1/+1
\|
*	Linux 3.18.93v3.18.93	Greg Kroah-Hartman	2018-01-31	1	-1/+1
\|
*	Linux 3.18.92v3.18.92	Greg Kroah-Hartman	2018-01-17	1	-1/+1
\|
*	Linux 3.18.91v3.18.91	Greg Kroah-Hartman	2018-01-02	1	-1/+1
\|
*	kbuild: add '-fno-stack-check' to kernel build options	Linus Torvalds	2018-01-02	1	-0/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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>
*	Linux 3.18.90v3.18.90	Greg Kroah-Hartman	2017-12-25	1	-1/+1
\|
*	Linux 3.18.89v3.18.89	Greg Kroah-Hartman	2017-12-20	1	-1/+1
\|
*	Linux 3.18.88v3.18.88	Greg Kroah-Hartman	2017-12-16	1	-1/+1
\|
*	Linux 3.18.87v3.18.87	Greg Kroah-Hartman	2017-12-09	1	-1/+1
\|
*	Linux 3.18.86v3.18.86	Greg Kroah-Hartman	2017-12-05	1	-1/+1
\|
*	Linux 3.18.85v3.18.85	Greg Kroah-Hartman	2017-11-30	1	-1/+1
\|
*	Linux 3.18.84v3.18.84	Greg Kroah-Hartman	2017-11-24	1	-1/+1
\|
*	Linux 3.18.83v3.18.83	Greg Kroah-Hartman	2017-11-21	1	-1/+1
\|
*	Linux 3.18.82v3.18.82	Greg Kroah-Hartman	2017-11-18	1	-1/+1
\|
*	Linux 3.18.81v3.18.81	Greg Kroah-Hartman	2017-11-15	1	-1/+1
\|
*	Linux 3.18.80v3.18.80	Greg Kroah-Hartman	2017-11-08	1	-1/+1
\|
*	Linux 3.18.79v3.18.79	Greg Kroah-Hartman	2017-11-02	1	-1/+1
\|
*	Linux 3.18.78v3.18.78	Greg Kroah-Hartman	2017-10-27	1	-1/+1
\|
*	Linux 3.18.77v3.18.77	Greg Kroah-Hartman	2017-10-21	1	-1/+1
\|
*	Linux 3.18.76v3.18.76	Greg Kroah-Hartman	2017-10-18	1	-1/+1
\|
*	Linux 3.18.75v3.18.75	Greg Kroah-Hartman	2017-10-12	1	-1/+1
\|
*	Linux 3.18.74v3.18.74	Greg Kroah-Hartman	2017-10-08	1	-1/+1
\|
*	Linux 3.18.73v3.18.73	Greg Kroah-Hartman	2017-10-05	1	-1/+1
\|
*	Linux 3.18.72v3.18.72	Greg Kroah-Hartman	2017-09-27	1	-1/+1
\|
*	Linux 3.18.71v3.18.71	Greg Kroah-Hartman	2017-09-13	1	-1/+1
\|
*	Linux 3.18.70v3.18.70	Greg Kroah-Hartman	2017-09-07	1	-1/+1
\|
*	Linux 3.18.69v3.18.69	Greg Kroah-Hartman	2017-09-02	1	-1/+1
\|
*	Linux 3.18.68v3.18.68	Greg Kroah-Hartman	2017-08-30	1	-1/+1
\|
*	Linux 3.18.67v3.18.67	Greg Kroah-Hartman	2017-08-24	1	-1/+1
\|
*	Linux 3.18.66v3.18.66	Greg Kroah-Hartman	2017-08-16	1	-1/+1
\|
*	Linux 3.18.65v3.18.65	Greg Kroah-Hartman	2017-08-12	1	-1/+1
\|
*	Linux 3.18.64v3.18.64	Greg Kroah-Hartman	2017-08-11	1	-1/+1
\|
*	Linux 3.18.63v3.18.63	Greg Kroah-Hartman	2017-07-27	1	-1/+1
\|
*	disable new gcc-7.1.1 warnings for now	Linus Torvalds	2017-07-27	1	-0/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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>
*	Linux 3.18.62v3.18.62	Greg Kroah-Hartman	2017-07-21	1	-1/+1
\|
*	Linux 3.18.61v3.18.61	Greg Kroah-Hartman	2017-07-15	1	-1/+1
\|
*	Linux 3.18.60v3.18.60	Greg Kroah-Hartman	2017-07-05	1	-1/+1
\|
*	Linux 3.18.59v3.18.59	Greg Kroah-Hartman	2017-06-29	1	-1/+1
\|
*	Linux 3.18.58v3.18.58	Greg Kroah-Hartman	2017-06-26	1	-1/+1
\|
*	Linux 3.18.57v3.18.57	Greg Kroah-Hartman	2017-06-14	1	-1/+1
\|
*	Linux 3.18.56v3.18.56	Greg Kroah-Hartman	2017-06-07	1	-1/+1
\|
*	Linux 3.18.55v3.18.55	Greg Kroah-Hartman	2017-05-25	1	-1/+1
\|
*	Linux 3.18.54v3.18.54	Greg Kroah-Hartman	2017-05-20	1	-1/+1
\|
*	Linux 3.18.53v3.18.53	Greg Kroah-Hartman	2017-05-15	1	-1/+1
\|