public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug
Date: Fri, 26 Oct 2012 03:29:59 -0500	[thread overview]
Message-ID: <508A4A07.2050007@gmail.com> (raw)
In-Reply-To: <20121026013435.184fcaf3@digimed.co.uk>

Neil Bothwick wrote:
> On Thu, 25 Oct 2012 15:10:17 -0500, Dale wrote:
>
>> Or just don't update the kernel until it is fixed. After all, if the
>> kernel you are using works and is not a serious security problem, just
>> use it for a while.  They will fix it pretty soon I'm sure. 
> Several versions are affected, it's not a new issue, just a newly
> discovered one. That in itself indicates the likelihood of being affected
> by it, considering how many boxes use ext4 with these kernel versions.
>
>

My point is, if you are using a version that is not affected, keep using
it, don't upgrade yet.  I saw a list of the affected versions.  Just
avoid those for now.  Is it a perfect plan, of course not.  It's better
than nothing tho.  It's certainly better than using a known version with
this problem.  If a person is using an affected version, then I would
reboot to another kernel that is not on the list. 

Now if someone wants to keep using a known version that is affected,
that's their thing.  Since I don't reboot much, it would likely not
affect me either way.  Thing is, I'm not going to take the chance either
way.  That is of course if the problem is what I read and not something
else all together.  The problem seems to be a moving target since it is
not exactly known yet.

Either way, having the information is better than nothing.  Avoiding the
affected versions is better than nothing.  None of this may matter
depending on all sorts of things.  Me, I'm going to stick with what I am
using, that's not on the affected list so far, and wait until whatever
version has a known fix.  That's my plan for now, subject to change if
the situation changes. 

Oh, going to cross fingers too. ;-) 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!



  reply	other threads:[~2012-10-26  8:31 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 [this message]
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=508A4A07.2050007@gmail.com \
    --to=rdalek1967@gmail.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