public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug
Date: Wed, 24 Oct 2012 11:22:59 -0400	[thread overview]
Message-ID: <1000.1351092179@ccs.covici.com> (raw)
In-Reply-To: <5087FE72.7060002@gmail.com>


Dale <rdalek1967@gmail.com> wrote:

> Nikos Chantziaras wrote:
> > Kernels 3.4, 3.5, and 3.6 can result in severe data corruption if
> > you're using the EXT4 filesystem:
> >
> > http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ
> >
> > This includes gentoo-sources.  I hope the Gentoo developers are on top
> > of this.  In the meantime, avoid doing reboots after too short an uptime.
> >
> >
> >
> 
> Oh crap.  O_O 
> 
> This is one of those times I am glad I am not a shutdown/restart nut.  lol 
> 
> root@fireball / # uptime
>  09:39:19 up 32 days,  1:48,  5 users,  load average: 0.35, 0.35, 0.44
> root@fireball / #
> 
> Should be safe enough by now.  I wonder what version will have the fix
> tho?  3.7?  3.8?  They move pretty quick tho.  That's good. 
> 
> Thanks for the heads up. 
> 
> Dale, not going to panic yet. 
> 
> :-)  :-) 
> 
> -- 
> I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
> 
What git tree is this -- maybe I can get the diff and reverse patch till
a newer version comes out?


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com


  reply	other threads:[~2012-10-24 15:24 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 13:54 [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug Nikos Chantziaras
2012-10-24 14:42 ` Dale
2012-10-24 15:22   ` covici [this message]
2012-10-24 14:43 ` Paul Hartman
2012-10-24 14:48 ` Markos Chandras
2012-10-24 18:10 ` Bruce Hill
2012-10-24 22:36   ` john
2012-10-24 23:55     ` mindrunner
2012-10-25  0:55 ` Canek Peláez Valdés
2012-10-25  1:09   ` Kerin Millar
2012-10-25  1:32     ` Canek Peláez Valdés
2012-10-25  1:38     ` Canek Peláez Valdés
2012-10-25  2:51       ` Kerin Millar
2012-10-25  3:03         ` Michael Mol
2012-10-25 19:40           ` Pandu Poluan
2012-10-25 20:10             ` Dale
2012-10-26  0:34               ` Neil Bothwick
2012-10-26  8:29                 ` Dale
2012-10-27 19:16                 ` Volker Armin Hemmann
2012-10-28 17:12                   ` Mark Knecht
2012-10-26  3:26               ` Pandu Poluan
2012-10-26  8:16                 ` Dale
2012-10-25 20:33             ` Mark Knecht
2012-10-26  3:30               ` Pandu Poluan
2012-10-25 23:10             ` Michael Mol
2012-10-26  3:37               ` Pandu Poluan
2012-10-25  3:04         ` Canek Peláez Valdés
2012-10-25  4:43           ` [gentoo-user] " Nikos Chantziaras
2012-10-25 14:26         ` Grant Edwards
2012-10-25 16:53           ` Remy Blank
2012-10-25 21:04           ` Kerin Millar
2012-10-27 18:19             ` Volker Armin Hemmann
2012-10-27 18:28               ` Canek Peláez Valdés
2012-10-29 10:29 ` [gentoo-user] " Helmut Jarausch
2012-11-02 13:45   ` Kerin Millar
2012-11-02 14:55     ` Dale
2012-11-02 15:05       ` Michael Mol
2012-11-02 15:08       ` Paul Hartman
2012-11-02 16:08       ` Kerin Millar
2012-11-02 20:19         ` Dale

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=1000.1351092179@ccs.covici.com \
    --to=covici@ccs.covici.com \
    --cc=gentoo-user@lists.gentoo.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