From: Pavel Machek <pavel@ucw.cz>
To: Daniel Micay <danielmicay@gmail.com>
Cc: "Kees Cook" <keescook@chromium.org>,
"Tony Lindgren" <tony@atomide.com>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
pali.rohar@gmail.com, sre@kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, "Kevin Hilman" <khilman@kernel.org>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
ivo.g.dimitrov.75@gmail.com,
"Patrik Bachan" <patrikbachan@gmail.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Mickuláš Qwertz" <abcloriens@gmail.com>,
"Clayton Craft" <clayton@craftyguy.net>
Subject: Re: [regression v4.17-rc0] Re: FORTIFY_SOURCE breaks ARM compilation in -next -- was Re: ARM compile failure in Re: linux-next: Tree for Apr 4
Date: Fri, 20 Apr 2018 22:30:09 +0200 [thread overview]
Message-ID: <20180420203009.GA2244@amd> (raw)
In-Reply-To: <CA+DvKQ+ekrr51_JcPiGrOaHj79NxYUqLWEo97z97tSuUzcuoZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Fri 2018-04-20 15:30:03, Daniel Micay wrote:
> Well, that's not related, it's just this:
>
> #ifdef __GNUC__
> #if (__GNUC__ == 3 && __GNUC_MINOR__ < 3)
> #error Your compiler is too buggy; it is known to miscompile kernels.
> #error Known good compilers: 3.3, 4.x
> #endif
> #if GCC_VERSION >= 40800 && GCC_VERSION < 40803
> #error Your compiler is too buggy; it is known to miscompile kernels
> #error and result in filesystem corruption and oopses.
> #endif
> #endif
Yeah, I know. I guess the kernel would compile if I removed those
checks...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [regression v4.17-rc0] Re: FORTIFY_SOURCE breaks ARM compilation in -next -- was Re: ARM compile failure in Re: linux-next: Tree for Apr 4
Date: Fri, 20 Apr 2018 22:30:09 +0200 [thread overview]
Message-ID: <20180420203009.GA2244@amd> (raw)
In-Reply-To: <CA+DvKQ+ekrr51_JcPiGrOaHj79NxYUqLWEo97z97tSuUzcuoZg@mail.gmail.com>
On Fri 2018-04-20 15:30:03, Daniel Micay wrote:
> Well, that's not related, it's just this:
>
> #ifdef __GNUC__
> #if (__GNUC__ == 3 && __GNUC_MINOR__ < 3)
> #error Your compiler is too buggy; it is known to miscompile kernels.
> #error Known good compilers: 3.3, 4.x
> #endif
> #if GCC_VERSION >= 40800 && GCC_VERSION < 40803
> #error Your compiler is too buggy; it is known to miscompile kernels
> #error and result in filesystem corruption and oopses.
> #endif
> #endif
Yeah, I know. I guess the kernel would compile if I removed those
checks...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180420/988bf88a/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Micay <danielmicay@gmail.com>
Cc: "Kees Cook" <keescook@chromium.org>,
"Tony Lindgren" <tony@atomide.com>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
pali.rohar@gmail.com, sre@kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, "Kevin Hilman" <khilman@kernel.org>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
ivo.g.dimitrov.75@gmail.com,
"Patrik Bachan" <patrikbachan@gmail.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Mickuláš Qwertz" <abcloriens@gmail.com>,
"Clayton Craft" <clayton@craftyguy.net>,
"Martijn Braam" <martijn@brixit.nl>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Filip Matijević" <filip.matijevic.pz@gmail.com>,
"Jinbum Park" <jinb.park7@gmail.com>,
"Russell King" <rmk+kernel@armlinux.org.uk>
Subject: Re: [regression v4.17-rc0] Re: FORTIFY_SOURCE breaks ARM compilation in -next -- was Re: ARM compile failure in Re: linux-next: Tree for Apr 4
Date: Fri, 20 Apr 2018 22:30:09 +0200 [thread overview]
Message-ID: <20180420203009.GA2244@amd> (raw)
In-Reply-To: <CA+DvKQ+ekrr51_JcPiGrOaHj79NxYUqLWEo97z97tSuUzcuoZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Fri 2018-04-20 15:30:03, Daniel Micay wrote:
> Well, that's not related, it's just this:
>
> #ifdef __GNUC__
> #if (__GNUC__ == 3 && __GNUC_MINOR__ < 3)
> #error Your compiler is too buggy; it is known to miscompile kernels.
> #error Known good compilers: 3.3, 4.x
> #endif
> #if GCC_VERSION >= 40800 && GCC_VERSION < 40803
> #error Your compiler is too buggy; it is known to miscompile kernels
> #error and result in filesystem corruption and oopses.
> #endif
> #endif
Yeah, I know. I guess the kernel would compile if I removed those
checks...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-04-20 20:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 6:55 linux-next: Tree for Apr 4 Stephen Rothwell
2018-04-04 7:48 ` ARM compile failure in " Pavel Machek
2018-04-04 7:48 ` Pavel Machek
2018-04-04 17:58 ` Tony Lindgren
2018-04-04 17:58 ` Tony Lindgren
2018-04-04 18:15 ` Pavel Machek
2018-04-04 18:15 ` Pavel Machek
2018-04-04 18:46 ` Pavel Machek
2018-04-04 18:46 ` Pavel Machek
2018-04-04 19:59 ` Tony Lindgren
2018-04-04 19:59 ` Tony Lindgren
2018-04-04 20:18 ` FORTIFY_SOURCE breaks ARM compilation in -next -- was " Pavel Machek
2018-04-04 20:18 ` Pavel Machek
2018-04-15 17:39 ` [regression v4.17-rc0] " Pavel Machek
2018-04-15 17:39 ` Pavel Machek
2018-04-15 18:00 ` Kees Cook
2018-04-15 18:00 ` Kees Cook
2018-04-15 18:00 ` Kees Cook
2018-04-15 20:58 ` Pavel Machek
2018-04-15 20:58 ` Pavel Machek
2018-04-15 20:58 ` Pavel Machek
2018-04-20 7:34 ` Pavel Machek
2018-04-20 7:34 ` Pavel Machek
2018-04-20 7:34 ` Pavel Machek
2018-04-20 15:05 ` Kees Cook
2018-04-20 15:05 ` Kees Cook
2018-04-20 15:05 ` Kees Cook
2018-04-20 17:21 ` Russell King - ARM Linux
2018-04-20 17:21 ` Russell King - ARM Linux
2018-04-20 17:21 ` Russell King - ARM Linux
2018-04-20 19:15 ` Pavel Machek
2018-04-20 19:15 ` Pavel Machek
2018-04-20 19:15 ` Pavel Machek
2018-04-20 19:18 ` Daniel Micay
2018-04-20 19:18 ` Daniel Micay
2018-04-20 19:18 ` Daniel Micay
2018-04-20 19:28 ` Pavel Machek
2018-04-20 19:28 ` Pavel Machek
2018-04-20 19:28 ` Pavel Machek
2018-04-20 19:30 ` Daniel Micay
2018-04-20 19:30 ` Daniel Micay
2018-04-20 19:30 ` Daniel Micay
2018-04-20 20:30 ` Pavel Machek [this message]
2018-04-20 20:30 ` Pavel Machek
2018-04-20 20:30 ` Pavel Machek
2018-04-04 7:50 ` x32 suspend failuer " Pavel Machek
2018-04-04 7:58 ` Rafael J. Wysocki
2018-04-04 8:49 ` Pavel Machek
2018-04-05 12:25 ` update-binfmts breaking suspend was " Pavel Machek
2018-04-05 20:30 ` Pavel Machek
2018-04-05 20:30 ` Pavel Machek
2018-04-05 22:27 ` Rafael J. Wysocki
[not found] ` <SN4PR2101MB073673B12998428D48DA62E5CBBA0@SN4PR2101MB0736.namprd21.prod.outlook.com>
[not found] ` <20180406144355.GA20605@bombadil.infradead.org>
2018-04-11 4:30 ` update-binfmts breaking suspend Matthew Wilcox
2018-04-11 6:09 ` Pavel Machek
2018-04-06 22:41 ` x32 suspend failuer in Re: linux-next: Tree for Apr 4 Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180420203009.GA2244@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=arnd@arndb.de \
--cc=clayton@craftyguy.net \
--cc=danielmicay@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=keescook@chromium.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=regressions@leemhuis.info \
--cc=serge@hallyn.com \
--cc=sfr@canb.auug.org.au \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.