public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.22-rc3 safe to migrate to?
Date: Sat, 02 Jun 2007 23:30:49 -0700	[thread overview]
Message-ID: <46626019.3070807@goop.org> (raw)
In-Reply-To: <alpine.DEB.0.99.0706030115410.16496@sheep.housecafe.de>

Christian Kujau wrote:
> Just for the record, you mean this one:
> http://lkml.org/lkml/2007/5/12/93   ..right? (haven't been bitten by
> this one...yet)

That's the one.  It's fairly subtle; there's no metadata/filesystem
corruption, and the file just reverts back to a previous length, so if
it were append-only, it would just return to a previous state.

    J

  parent reply	other threads:[~2007-06-03  6:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 21:24 Kernel 2.6.22-rc3 safe to migrate to? Justin Piszcz
2007-06-02 21:59 ` Christian Kujau
2007-06-02 22:09   ` Justin Piszcz
2007-06-02 22:27   ` Justin Piszcz
2007-06-02 22:54 ` Jeremy Fitzhardinge
2007-06-02 22:55   ` Justin Piszcz
2007-06-03  0:25     ` Christian Kujau
2007-06-03  0:27       ` Justin Piszcz
2007-06-03  6:30       ` Jeremy Fitzhardinge [this message]
     [not found]   ` <6bffcb0e0706030059o3e53e647uf3ae1aa3f16609d8@mail.gmail.com>
2007-06-03  8:02     ` Jeremy Fitzhardinge
2007-06-03  8:41       ` Justin Piszcz
     [not found] <fa.eE9c0s9eXX/aO2N8hiu3e2Yehz8@ifi.uio.no>
     [not found] ` <fa.hq4JzIoUe01l8ywIZPkqjocRBmc@ifi.uio.no>
     [not found]   ` <fa.3aN+T/xQVA3sf9DdMPLOfUVmYA0@ifi.uio.no>
     [not found]     ` <fa.mJ71j4nyi6ALIkQjLcpIJtTbVVI@ifi.uio.no>
     [not found]       ` <fa.vxJKq726YMWJY2i/waKQsNec3aU@ifi.uio.no>
2007-06-03  6:23         ` Robert Hancock

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=46626019.3070807@goop.org \
    --to=jeremy@goop.org \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox