From: Peter Zijlstra <peterz@infradead.org>
To: Alessandro Bono <alessandro.bono@gmail.com>
Cc: linux-xfs <linux-xfs@oss.sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4
Date: Mon, 09 Feb 2009 11:33:27 +0100 [thread overview]
Message-ID: <1234175607.5951.76.camel@laptop> (raw)
In-Reply-To: <1234135463.12370.47.camel@champagne.cantina>
On Mon, 2009-02-09 at 00:24 +0100, Alessandro Bono wrote:
> In the past I lose configuration files from kde, gconf based programs
> (gnome), pan, firefox, etc
> maybe xfs expose more this problem
>From what I heard Linux userspace is on crack and thinks it can get away
without calling fsync().
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Alessandro Bono <alessandro.bono@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@oss.sgi.com>
Subject: Re: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4
Date: Mon, 09 Feb 2009 11:33:27 +0100 [thread overview]
Message-ID: <1234175607.5951.76.camel@laptop> (raw)
In-Reply-To: <1234135463.12370.47.camel@champagne.cantina>
On Mon, 2009-02-09 at 00:24 +0100, Alessandro Bono wrote:
> In the past I lose configuration files from kde, gconf based programs
> (gnome), pan, firefox, etc
> maybe xfs expose more this problem
>From what I heard Linux userspace is on crack and thinks it can get away
without calling fsync().
next prev parent reply other threads:[~2009-02-09 10:34 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 13:06 XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4 Alessandro Bono
2009-02-07 13:06 ` Alessandro Bono
2009-02-08 22:16 ` Dave Chinner
2009-02-08 22:16 ` Dave Chinner
2009-02-08 23:24 ` Alessandro Bono
2009-02-08 23:24 ` Alessandro Bono
2009-02-09 8:40 ` Michael Monnerie
2009-02-09 10:33 ` Peter Zijlstra [this message]
2009-02-09 10:33 ` Peter Zijlstra
2009-02-08 22:28 ` Christoph Hellwig
2009-02-08 22:28 ` Christoph Hellwig
2009-02-08 22:39 ` Alessandro Bono
2009-02-08 22:39 ` Alessandro Bono
2009-02-08 22:42 ` Christoph Hellwig
2009-02-08 22:42 ` Christoph Hellwig
2009-02-08 22:45 ` Alessandro Bono
2009-02-08 22:45 ` Alessandro Bono
2009-02-09 2:52 ` Eric Sandeen
2009-02-09 2:52 ` Eric Sandeen
2009-02-09 2:53 ` Eric Sandeen
2009-02-09 2:53 ` Eric Sandeen
2009-02-09 7:53 ` Christoph Hellwig
2009-02-09 7:53 ` Christoph Hellwig
2009-02-09 9:02 ` Alessandro Bono
2009-02-09 9:02 ` Alessandro Bono
2009-02-10 10:43 ` Dave Chinner
2009-02-10 10:43 ` Dave Chinner
2009-02-10 10:53 ` Alessandro Bono
2009-02-10 10:53 ` Alessandro Bono
2009-02-11 21:47 ` Alessandro Bono
2009-02-11 21:47 ` Alessandro Bono
2009-02-12 9:47 ` Alessandro Bono
2009-02-12 9:47 ` Alessandro Bono
2009-02-13 9:19 ` Michael Monnerie
2009-02-26 16:58 ` Jan Kara
2009-02-26 16:58 ` Jan Kara
2009-02-26 16:59 ` Jan Kara
2009-02-26 16:59 ` Jan Kara
2009-02-27 9:22 ` Alessandro Bono
2009-02-27 9:22 ` Alessandro Bono
2009-02-27 19:44 ` Alessandro Bono
2009-02-27 19:44 ` Alessandro Bono
2009-03-02 13:36 ` Jan Kara
2009-03-02 13:36 ` Jan Kara
2009-03-02 15:04 ` Alessandro Bono
2009-03-02 15:04 ` Alessandro Bono
2009-03-11 17:04 ` Alessandro Bono
2009-03-11 17:04 ` Alessandro Bono
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=1234175607.5951.76.camel@laptop \
--to=peterz@infradead.org \
--cc=alessandro.bono@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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.