public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Kerin Millar <kerframil@fastmail.co.uk>
Subject: Re: [gentoo-user] Re: Heads-up: Several kernel versions have severe EXT4 data corruption bug
Date: Sat, 27 Oct 2012 13:28:05 -0500	[thread overview]
Message-ID: <CADPrc82R1SZTw-ASFiWVDJLk=SOq9KQYQntgeNUttzpGw=ucKg@mail.gmail.com> (raw)
In-Reply-To: <1530096.TJQ2ZnIPGe@energy>

On Sat, Oct 27, 2012 at 1:19 PM, Volker Armin Hemmann
<volkerarmin@googlemail.com> wrote:
[snip]
> and that ONLY two people who did some REALLY stupid stuff to stumble over that
> bug are hit by it, should tell you something.

Actually, it seems only *one* person can reliably reproduce this bug:

https://plus.google.com/u/0/117091380454742934025/posts/f5a1eHxUzSh

"The problem is no one other than one person who is using non-standard
mount options (which I should have disabled by default, because they
are known to be problematic) has been able to reliably reproduce the
problem."

But there is a lot of news sites who'll never miss a chance to scream
that the sky is falling. I don't think we'll see this last update from
Ted neither on Slashdot nor in Phoronix.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México


  reply	other threads:[~2012-10-27 18:29 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
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 [this message]
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='CADPrc82R1SZTw-ASFiWVDJLk=SOq9KQYQntgeNUttzpGw=ucKg@mail.gmail.com' \
    --to=caneko@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=kerframil@fastmail.co.uk \
    /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