From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Rik van Riel <riel@redhat.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>,
josh@joshtriplett.org, Rabin Vincent <rabin@rab.in>,
Alan Stern <stern@rowland.harvard.edu>,
Johannes Weiner <hannes@cmpxchg.org>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: RCU bug with v3.17-rc3 ?
Date: Sat, 11 Oct 2014 14:27:36 -0500 [thread overview]
Message-ID: <543984A8.8050701@mentor.com> (raw)
In-Reply-To: <54388B81.5020306@mentor.com>
On 10/10/2014 08:44 PM, Nathan Lynch wrote:
> On 10/10/2014 11:25 AM, Russell King - ARM Linux wrote:
>>
>> Right, so GCC 4.8.{1,2} are totally unsuitable for kernel building (and
>> it seems that this has been known about for some time.)
>
> Looking at http://gcc.gnu.org/PR58854 it seems that all 4.8.x for x < 3
> are affected, as well as 4.9.0.
Correction -- 4.9.0 has this fixed, even though the GCC PR shows it as a
"known to fail" version.
WARNING: multiple messages have this Message-ID (diff)
From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: RCU bug with v3.17-rc3 ?
Date: Sat, 11 Oct 2014 14:27:36 -0500 [thread overview]
Message-ID: <543984A8.8050701@mentor.com> (raw)
In-Reply-To: <54388B81.5020306@mentor.com>
On 10/10/2014 08:44 PM, Nathan Lynch wrote:
> On 10/10/2014 11:25 AM, Russell King - ARM Linux wrote:
>>
>> Right, so GCC 4.8.{1,2} are totally unsuitable for kernel building (and
>> it seems that this has been known about for some time.)
>
> Looking at http://gcc.gnu.org/PR58854 it seems that all 4.8.x for x < 3
> are affected, as well as 4.9.0.
Correction -- 4.9.0 has this fixed, even though the GCC PR shows it as a
"known to fail" version.
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Rik van Riel <riel@redhat.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>, <josh@joshtriplett.org>,
Rabin Vincent <rabin@rab.in>,
Alan Stern <stern@rowland.harvard.edu>,
Johannes Weiner <hannes@cmpxchg.org>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: RCU bug with v3.17-rc3 ?
Date: Sat, 11 Oct 2014 14:27:36 -0500 [thread overview]
Message-ID: <543984A8.8050701@mentor.com> (raw)
In-Reply-To: <54388B81.5020306@mentor.com>
On 10/10/2014 08:44 PM, Nathan Lynch wrote:
> On 10/10/2014 11:25 AM, Russell King - ARM Linux wrote:
>>
>> Right, so GCC 4.8.{1,2} are totally unsuitable for kernel building (and
>> it seems that this has been known about for some time.)
>
> Looking at http://gcc.gnu.org/PR58854 it seems that all 4.8.x for x < 3
> are affected, as well as 4.9.0.
Correction -- 4.9.0 has this fixed, even though the GCC PR shows it as a
"known to fail" version.
next prev parent reply other threads:[~2014-10-11 19:27 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 18:40 RCU bug with v3.17-rc3 ? Felipe Balbi
2014-09-04 19:16 ` Paul E. McKenney
2014-09-04 19:25 ` Felipe Balbi
2014-09-04 20:04 ` Felipe Balbi
2014-09-05 21:32 ` Paul E. McKenney
2014-10-08 17:13 ` Felipe Balbi
2014-10-08 17:13 ` Felipe Balbi
2014-10-08 17:13 ` Felipe Balbi
2014-10-08 17:57 ` Felipe Balbi
2014-10-08 17:57 ` Felipe Balbi
2014-10-08 17:57 ` Felipe Balbi
2014-10-08 21:29 ` Felipe Balbi
2014-10-08 21:29 ` Felipe Balbi
2014-10-08 21:29 ` Felipe Balbi
2014-10-09 16:01 ` Johannes Weiner
2014-10-09 16:01 ` Johannes Weiner
[not found] ` <20141009160138.GA2396-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2014-10-09 16:26 ` Felipe Balbi
2014-10-09 16:26 ` Felipe Balbi
2014-10-09 16:26 ` Felipe Balbi
2014-10-09 20:35 ` Felipe Balbi
2014-10-09 20:35 ` Felipe Balbi
2014-10-09 20:35 ` Felipe Balbi
2014-10-09 20:41 ` Rabin Vincent
2014-10-09 20:41 ` Rabin Vincent
2014-10-09 20:46 ` Felipe Balbi
2014-10-09 20:46 ` Felipe Balbi
2014-10-09 20:46 ` Felipe Balbi
2014-10-09 21:07 ` Felipe Balbi
2014-10-09 21:07 ` Felipe Balbi
2014-10-09 21:07 ` Felipe Balbi
2014-10-10 13:57 ` Felipe Balbi
2014-10-10 13:57 ` Felipe Balbi
2014-10-10 13:57 ` Felipe Balbi
2014-10-10 16:25 ` Russell King - ARM Linux
2014-10-10 16:25 ` Russell King - ARM Linux
[not found] ` <20141010162531.GL12379-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-10-11 1:44 ` Nathan Lynch
2014-10-11 1:44 ` Nathan Lynch
2014-10-11 1:44 ` Nathan Lynch
2014-10-11 2:40 ` Peter Hurley
2014-10-11 2:40 ` Peter Hurley
2014-10-11 3:54 ` Peter Chen
2014-10-11 3:54 ` Peter Chen
2014-10-11 3:54 ` Peter Chen
2014-10-11 14:16 ` Russell King - ARM Linux
2014-10-11 14:16 ` Russell King - ARM Linux
2014-10-11 14:16 ` Russell King - ARM Linux
2014-10-11 14:51 ` Otavio Salvador
2014-10-11 14:51 ` Otavio Salvador
2014-10-11 18:15 ` Peter Hurley
2014-10-11 18:15 ` Peter Hurley
[not found] ` <54388B81.5020306-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2014-10-11 14:14 ` Russell King - ARM Linux
2014-10-11 14:14 ` Russell King - ARM Linux
2014-10-11 14:14 ` Russell King - ARM Linux
2014-10-11 19:27 ` Nathan Lynch [this message]
2014-10-11 19:27 ` Nathan Lynch
2014-10-11 19:27 ` Nathan Lynch
2014-10-13 9:11 ` David Laight
2014-10-13 9:11 ` David Laight
2014-10-13 11:43 ` Russell King - ARM Linux
2014-10-13 11:43 ` Russell King - ARM Linux
2014-10-14 2:06 ` Greg KH
2014-10-14 2:06 ` Greg KH
2014-10-14 10:27 ` Peter Hurley
2014-10-14 10:27 ` Peter Hurley
[not found] ` <20141014020640.GB25433-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-10-15 21:23 ` Russell King - ARM Linux
2014-10-15 21:23 ` Russell King - ARM Linux
2014-10-15 21:23 ` Russell King - ARM Linux
[not found] ` <20141015212310.GP12379-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-10-15 21:25 ` Russell King - ARM Linux
2014-10-15 21:25 ` Russell King - ARM Linux
2014-10-15 21:25 ` Russell King - ARM Linux
2014-10-19 9:54 ` Russell King - ARM Linux
2014-10-19 9:54 ` Russell King - ARM Linux
2014-10-19 15:28 ` Felipe Balbi
2014-10-19 15:28 ` Felipe Balbi
2014-10-19 20:48 ` Olof Johansson
2014-10-19 20:48 ` Olof Johansson
2014-10-19 20:48 ` Olof Johansson
2014-10-09 21:47 ` Aaro Koskinen
2014-10-09 21:47 ` Aaro Koskinen
2014-10-10 16:18 ` Russell King - ARM Linux
2014-10-10 16:18 ` Russell King - ARM Linux
2014-10-10 20:52 ` Aaro Koskinen
2014-10-10 20:52 ` Aaro Koskinen
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=543984A8.8050701@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=akpm@linux-foundation.org \
--cc=balbi@ti.com \
--cc=hannes@cmpxchg.org \
--cc=josh@joshtriplett.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rabin@rab.in \
--cc=riel@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=stern@rowland.harvard.edu \
--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.