From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel 3.17.1-r1
Date: Sat, 18 Oct 2014 20:34:04 -0400 [thread overview]
Message-ID: <CAGfcS_m6SH95dQXgwf4O_-0kCJGAZGhS2UFfEtvErbCnqJXVgQ@mail.gmail.com> (raw)
In-Reply-To: <20141019002109.GA1023@ca.inter.net>
On Sat, Oct 18, 2014 at 8:21 PM, Philip Webb <purslow@ca.inter.net> wrote:
>
> (2) There's been a sudden masking of 3.17.0 in favor of 3.17.1-r1 ,
> now successfully running my machine.
>
Yup - the changelog mentions filesystem corruption issues but not
which, and I'm too lazy to check the patches. :)
However, anybody running btrfs on 3.17 should be on the lookout for
3.17.2 or deploying patches - there was a fairly nasty readonly
snapshot bug in 3.17 which is tracked for the next stable kernel. The
good news is that the patch prevents it from happening again, and
btrfs-progs-3.17 (not yet in portage) repairs it.
--
Rich
prev parent reply other threads:[~2014-10-19 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 0:21 [gentoo-user] Kernel 3.17.1-r1 Philip Webb
2014-10-19 0:34 ` Rich Freeman [this message]
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=CAGfcS_m6SH95dQXgwf4O_-0kCJGAZGhS2UFfEtvErbCnqJXVgQ@mail.gmail.com \
--to=rich0@gentoo.org \
--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