All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Carsten Aulbert <carsten.aulbert@aei.mpg.de>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14)
Date: Thu, 19 Feb 2009 13:01:58 +0100	[thread overview]
Message-ID: <20090219120158.GA1747@wotan.suse.de> (raw)
In-Reply-To: <20090219061925.GE8830@disturbed>

On Thu, Feb 19, 2009 at 05:19:25PM +1100, Dave Chinner wrote:
> On Wed, Feb 18, 2009 at 10:36:59AM +0100, Carsten Aulbert wrote:
> > >> plus a few more nodes showing the same characteristics 
> > > 
> > > Hmmmm. Did this show up in 2.6.27.10? Or did it start occurring only
> > > after you upgraded from .10 to .14?
> > 
> > As far as I can see this only happened after the upgrade about 14 days
> > ago. What strikes me odd is that we only had this occurring massively on
> > Monday and Tuesday this week.
> > 
> > I don't know if a certain access pattern could trigger this somehow.
> 
> I suspect so. We've already had XFS trigger one bug in the new
> lockless pagecache code, and the fix for that went in 2.6.27.11 -
> between the good version and the version that you've been seeing
> these memory corruptions on. I'm wondering if that fix exposed or
> introduced another bug that you've hit....

Highly unlikely. It only introduces constraints on how the
compiler may generate code, so it would have to be a compiler
bug to cause a bug I think.

I wonder how long you've been running with 2.6.27 based kernels
without corruption?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: Carsten Aulbert <carsten.aulbert@aei.mpg.de>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14)
Date: Thu, 19 Feb 2009 13:01:58 +0100	[thread overview]
Message-ID: <20090219120158.GA1747@wotan.suse.de> (raw)
In-Reply-To: <20090219061925.GE8830@disturbed>

On Thu, Feb 19, 2009 at 05:19:25PM +1100, Dave Chinner wrote:
> On Wed, Feb 18, 2009 at 10:36:59AM +0100, Carsten Aulbert wrote:
> > >> plus a few more nodes showing the same characteristics 
> > > 
> > > Hmmmm. Did this show up in 2.6.27.10? Or did it start occurring only
> > > after you upgraded from .10 to .14?
> > 
> > As far as I can see this only happened after the upgrade about 14 days
> > ago. What strikes me odd is that we only had this occurring massively on
> > Monday and Tuesday this week.
> > 
> > I don't know if a certain access pattern could trigger this somehow.
> 
> I suspect so. We've already had XFS trigger one bug in the new
> lockless pagecache code, and the fix for that went in 2.6.27.11 -
> between the good version and the version that you've been seeing
> these memory corruptions on. I'm wondering if that fix exposed or
> introduced another bug that you've hit....

Highly unlikely. It only introduces constraints on how the
compiler may generate code, so it would have to be a compiler
bug to cause a bug I think.

I wonder how long you've been running with 2.6.27 based kernels
without corruption?

  parent reply	other threads:[~2009-02-19 12:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 14:49 xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14) Carsten Aulbert
2009-02-17 14:49 ` Carsten Aulbert
2009-02-17 15:19 ` Michael Monnerie
2009-02-17 15:56   ` Carsten Aulbert
2009-02-17 17:24 ` Eric Sandeen
2009-02-17 17:24   ` Eric Sandeen
2009-02-18  9:19 ` Dave Chinner
2009-02-18  9:19   ` Dave Chinner
2009-02-18  9:36   ` Carsten Aulbert
2009-02-18  9:36     ` Carsten Aulbert
2009-02-19  6:19     ` Dave Chinner
2009-02-19  6:19       ` Dave Chinner
2009-02-19 10:13       ` Carsten Aulbert
2009-02-19 10:13         ` Carsten Aulbert
2009-02-19 12:01       ` Nick Piggin [this message]
2009-02-19 12:01         ` Nick Piggin
2009-02-19 13:12         ` Carsten Aulbert
2009-02-19 13:12           ` Carsten Aulbert

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=20090219120158.GA1747@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=carsten.aulbert@aei.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /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.