public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: Adrian Bunk <bunk@kernel.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ext4@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kerneloops.org: 2.6.26-rc possible regression in ext3
Date: Thu, 19 Jun 2008 10:32:24 +0200	[thread overview]
Message-ID: <18522.6552.622680.92788@harpo.it.uu.se> (raw)
In-Reply-To: <20080619081146.GC17630@cs181133002.pp.htv.fi>

Adrian Bunk writes:
 > On Thu, Jun 19, 2008 at 03:42:34PM +1000, Dave Airlie wrote:
 > > On Thu, Jun 19, 2008 at 3:36 PM, Arjan van de Ven <arjan@linux.intel.com> wrote:
 > > > In the kerneloops.org stats, a new oops is rapidly climbing the charts.
 > > > The oops is a page fault in the ext3 "do_slit" function, and the first
 > > > report of it was with 2.6.26-rc6-git3.
 > > >
 > > > It happens with various applications; the backtraces are at:
 > > >
 > > > http://www.kerneloops.org/search.php?search=do_split
 > > 
 > > This is a bug in rawhide in gcc miscompiling something...
 > > 
 > > https://bugzilla.redhat.com/show_bug.cgi?id=451068
 > 
 > If I understand it correctly that's a bug in upstream gcc 4.3.1
 > (but not in gcc 4.3.0)?
 > 
 > Expect a lot more of this to pop up in the future.
 > Should we #error for gcc 4.3.1?

There are other nasty bugs in gcc-4.3.0. I actually
had to completely ban 4.3.0 in a user-space project
I'm involved with (Erlang) due to gcc PR36339 (fixed
in 4.3.1).

What's the gcc bugzilla number for this new 4.3.1 bug?

  reply	other threads:[~2008-06-19  8:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19  5:36 kerneloops.org: 2.6.26-rc possible regression in ext3 Arjan van de Ven
2008-06-19  5:42 ` Dave Airlie
2008-06-19  5:48   ` Arjan van de Ven
2008-06-19  6:42   ` Linus Torvalds
2008-06-19  7:09     ` Arjan van de Ven
2008-06-19  8:11   ` Adrian Bunk
2008-06-19  8:32     ` Mikael Pettersson [this message]
2008-06-19 10:49       ` Adrian Bunk
2008-06-19 13:40     ` Arjan van de Ven
2008-06-19 15:10       ` Adrian Bunk
2008-06-19 15:18         ` Arjan van de Ven
2008-06-19 15:25           ` Adrian Bunk
2008-06-19 15:27             ` Arjan van de Ven
2008-06-19 15:43               ` Adrian Bunk
2008-06-19 14:00 ` Eric Sandeen
2008-06-19 14:07   ` Arjan van de Ven
2008-06-19 14:17     ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2008-06-19  5:34 Arjan van de Ven
2008-06-19  6:01 ` Linus Torvalds
2008-06-19  6:09   ` Arjan van de Ven
2008-06-19  6:14   ` Linus Torvalds
2008-06-19  6:40     ` Linus Torvalds
2008-06-20 15:34   ` Bill Nottingham

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=18522.6552.622680.92788@harpo.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bunk@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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