From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Shriramana Sharma <samjnaa@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Distro vs latest kernel for BTRFS?
Date: Fri, 22 Aug 2014 08:04:12 -0400 [thread overview]
Message-ID: <53F731BC.6000200@gmail.com> (raw)
In-Reply-To: <CAH-HCWVMO+NO0B5i0o0gCHBy9dLjc08gcqxT7oEV5WkO2BHvMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On 2014-08-22 07:59, Shriramana Sharma wrote:
> Hello. I've seen repeated advices to use the latest kernel. While
> hearing of the recent compression bug affecting recent kernels does
> somewhat warn one off the previous advice, I would like to know what
> people who are running regular distros do to get the latest kernel.
>
> Personally I'm on Kubuntu, which provides mainline kernels till a
> particular point but not beyond that.
>
> Do people here always compile the latest kernel themselves just to get
> the latest BTRFS stability fixes (and improvements, though as a
> second priority)?
>
I personally use Gentoo Unstable on all my systems, so I build all my
kernels locally anyway, and stay pretty much in-line with the current
stable Mainline kernel.
Interestingly, I haven't had any issues related to either of the
recently discovered bugs, despite meeting all of the criteria for being
affected by them.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
next prev parent reply other threads:[~2014-08-22 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 11:59 Distro vs latest kernel for BTRFS? Shriramana Sharma
2014-08-22 12:04 ` Austin S Hemmelgarn [this message]
2014-08-22 18:09 ` Duncan
2014-08-22 18:22 ` Rich Freeman
2014-08-22 19:18 ` Austin S Hemmelgarn
2014-08-22 14:10 ` Marc MERLIN
2014-08-22 16:51 ` Chris Murphy
2014-08-22 17:38 ` Martin Steigerwald
2014-08-25 1:06 ` Qu Wenruo
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=53F731BC.6000200@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=samjnaa@gmail.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;
as well as URLs for NNTP newsgroup(s).