public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Rabin Vincent <rabin@rab.in>, 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>,
	josh@joshtriplett.org, Felipe Balbi <balbi@ti.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	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: Fri, 10 Oct 2014 17:18:35 +0100	[thread overview]
Message-ID: <20141010161835.GK12379@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20141009214706.GC4606@drone.musicnaut.iki.fi>

On Fri, Oct 10, 2014 at 12:47:06AM +0300, Aaro Koskinen wrote:
> Hi,
> 
> On Thu, Oct 09, 2014 at 10:41:01PM +0200, Rabin Vincent wrote:
> >   What GCC version are you using?
> >   
> >   4.8.1 and 4.8.2 are known to miscompile the ARM kernel and these
> >   find_get_entry() crashes with 0xffffffff involved smell a lot like the
> >   earlier reports from kernels build with those compilers:
> >   
> >   https://lkml.org/lkml/2014/6/25/456
> >   https://lkml.org/lkml/2014/6/30/375
> >   https://lkml.org/lkml/2014/6/30/660
> >   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854
> >   https://lkml.org/lkml/2014/5/9/330
> 
> Is it possible to blacklist those GCC versions on ARM somehow as it
> seems people are still using them?
> 
> This bug also ruined a file system on one of my boxes last year
> (see e.g. http://marc.info/?l=linux-arm-kernel&m=139033442527244&w=2).

Given that, why the fsck (pun intended) did you not shout a little louder
about getting it blacklisted.  Looking at your marc.info URL, there's
very little information there which hints at filesystem corruption, and
it's a thread of only *one* message according to marc.info.

Even _if_ I did read the message you point to above, that on its own did
not hint at filesystem corruption.

So, would you please mind passing on further details about this,
specifically which function in the ext4 code is affected, so it can
be properly written up.

Thanks.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2014-10-10 16:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140904184021.GA13421@saruman.home>
     [not found] ` <20140904191642.GJ5001@linux.vnet.ibm.com>
     [not found]   ` <20140904192535.GJ13421@saruman.home>
     [not found]     ` <20140904200403.GL13421@saruman.home>
     [not found]       ` <20140905213216.GD5001@linux.vnet.ibm.com>
2014-10-08 17:13         ` RCU bug with v3.17-rc3 ? Felipe Balbi
2014-10-08 17:57           ` Felipe Balbi
2014-10-08 21:29             ` Felipe Balbi
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 20:35                     ` Felipe Balbi
2014-10-09 20:41                     ` Rabin Vincent
2014-10-09 20:46                       ` Felipe Balbi
2014-10-09 21:07                         ` Felipe Balbi
2014-10-10 13:57                           ` Felipe Balbi
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  2:40                                   ` Peter Hurley
2014-10-11  3:54                                   ` Peter Chen
2014-10-11 14:16                                     ` Russell King - ARM Linux
2014-10-11 14:51                                       ` Otavio Salvador
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 19:27                                   ` Nathan Lynch
2014-10-13  9:11                                   ` David Laight
2014-10-13 11:43                                     ` Russell King - ARM Linux
2014-10-14  2:06                                       ` Greg KH
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
     [not found]                                             ` <20141015212310.GP12379-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-10-15 21:25                                               ` Russell King - ARM Linux
2014-10-19  9:54                                                 ` Russell King - ARM Linux
2014-10-19 15:28                                                   ` Felipe Balbi
2014-10-19 20:48                                                     ` Olof Johansson
2014-10-09 21:47                       ` Aaro Koskinen
2014-10-10 16:18                         ` Russell King - ARM Linux [this message]
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=20141010161835.GK12379@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=aaro.koskinen@iki.fi \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox