From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
Martin Steigerwald <martin@lichtvoll.de>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>,
"David Sterba" <dsterba@suse.cz>, Waxhead <waxhead@online.no>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: Is stability a joke? (wiki updated)
Date: Tue, 13 Sep 2016 07:28:38 -0400 [thread overview]
Message-ID: <f5a952b4-09d6-a8f8-161d-16f419c81cb1@gmail.com> (raw)
In-Reply-To: <CAJCQCtQ8a90dmtaHKLM=gG3PT_cixc1UZ21qHFhnMx37ovfOWw@mail.gmail.com>
On 2016-09-12 16:44, Chris Murphy wrote:
> On Mon, Sep 12, 2016 at 2:35 PM, Martin Steigerwald <martin@lichtvoll.de> wrote:
>> Am Montag, 12. September 2016, 23:21:09 CEST schrieb Pasi Kärkkäinen:
>>> On Mon, Sep 12, 2016 at 09:57:17PM +0200, Martin Steigerwald wrote:
>>>> Am Montag, 12. September 2016, 18:27:47 CEST schrieb David Sterba:
>>>>> On Mon, Sep 12, 2016 at 04:27:14PM +0200, David Sterba wrote:
>>>>>>> I therefore would like to propose that some sort of feature /
>>>>>>> stability
>>>>>>> matrix for the latest kernel is added to the wiki preferably
>>>>>>> somewhere
>>>>>>> where it is easy to find. It would be nice to archive old matrix'es
>>>>>>> as
>>>>>>> well in case someone runs on a bit older kernel (we who use Debian
>>>>>>> tend
>>>>>>> to like older kernels). In my opinion it would make things bit
>>>>>>> easier
>>>>>>> and perhaps a bit less scary too. Remember if you get bitten badly
>>>>>>> once
>>>>>>> you tend to stay away from from it all just in case, if you on the
>>>>>>> other
>>>>>>> hand know what bites you can safely pet the fluffy end instead :)
>>>>>>
>>>>>> Somebody has put that table on the wiki, so it's a good starting
>>>>>> point.
>>>>>> I'm not sure we can fit everything into one table, some combinations
>>>>>> do
>>>>>> not bring new information and we'd need n-dimensional matrix to get
>>>>>> the
>>>>>> whole picture.
>>>>>
>>>>> https://btrfs.wiki.kernel.org/index.php/Status
>>>>
>>>> Great.
>>>>
>>>> I made to minor adaption. I added a link to the Status page to my warning
>>>> in before the kernel log by feature page. And I also mentioned that at
>>>> the time the page was last updated the latest kernel version was 4.7.
>>>> Yes, thats some extra work to update the kernel version, but I think its
>>>> beneficial to explicitely mention the kernel version the page talks
>>>> about. Everyone who updates the page can update the version within a
>>>> second.
>>>
>>> Hmm.. that will still leave people wondering "but I'm running Linux 4.4, not
>>> 4.7, I wonder what the status of feature X is.."
>>>
>>> Should we also add a column for kernel version, so we can add "feature X is
>>> known to be OK on Linux 3.18 and later".. ? Or add those to "notes" field,
>>> where applicable?
>>
>> That was my initial idea, and it may be better than a generic kernel version
>> for all features. Even if we fill in 4.7 for any of the features that are
>> known to work okay for the table.
>>
>> For RAID 1 I am willing to say it works stable since kernel 3.14, as this was
>> the kernel I used when I switched /home and / to Dual SSD RAID 1 on this
>> ThinkPad T520.
>
> Just to cut yourself some slack, you could skip 3.14 because it's EOL
> now, and just go from 4.4.
That reminds me, we should probably make a point to make it clear that
this is for the _upstream_ mainline kernel versions, not for versions
from some arbitrary distro, and that people should check the distro's
documentation for that info.
next prev parent reply other threads:[~2016-09-13 11:28 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 8:55 Is stability a joke? Waxhead
2016-09-11 9:56 ` Steven Haigh
2016-09-11 10:23 ` Martin Steigerwald
2016-09-11 11:21 ` Zoiled
2016-09-11 11:43 ` Martin Steigerwald
2016-09-11 12:05 ` Martin Steigerwald
2016-09-11 12:39 ` Waxhead
2016-09-11 13:02 ` Hugo Mills
2016-09-11 14:59 ` Martin Steigerwald
2016-09-11 20:14 ` Chris Murphy
2016-09-12 12:20 ` Austin S. Hemmelgarn
2016-09-12 12:59 ` Michel Bouissou
2016-09-12 13:14 ` Austin S. Hemmelgarn
2016-09-12 14:04 ` Lionel Bouton
2016-09-15 1:05 ` Nicholas D Steeves
2016-09-15 8:02 ` Martin Steigerwald
2016-09-16 7:13 ` Helmut Eller
2016-09-15 5:55 ` Kai Krakow
2016-09-15 8:05 ` Martin Steigerwald
2016-09-11 14:54 ` Martin Steigerwald
2016-09-11 15:19 ` Martin Steigerwald
2016-09-11 20:21 ` Chris Murphy
2016-09-11 17:46 ` Marc MERLIN
2016-09-20 16:33 ` Chris Murphy
2016-09-11 17:11 ` Duncan
2016-09-12 12:26 ` Austin S. Hemmelgarn
2016-09-11 12:30 ` Waxhead
2016-09-11 14:36 ` Martin Steigerwald
2016-09-12 12:48 ` Swâmi Petaramesh
2016-09-12 13:53 ` Chris Mason
2016-09-12 17:36 ` Zoiled
2016-09-12 17:44 ` Waxhead
2016-09-15 1:12 ` Nicholas D Steeves
2016-09-12 14:27 ` David Sterba
2016-09-12 14:54 ` Austin S. Hemmelgarn
2016-09-12 16:51 ` David Sterba
2016-09-12 17:31 ` Austin S. Hemmelgarn
2016-09-15 1:07 ` Nicholas D Steeves
2016-09-15 1:13 ` Steven Haigh
2016-09-15 2:14 ` stability matrix (was: Is stability a joke?) Christoph Anton Mitterer
2016-09-15 9:49 ` stability matrix Hans van Kranenburg
2016-09-15 11:54 ` Austin S. Hemmelgarn
2016-09-15 14:15 ` Chris Murphy
2016-09-15 14:56 ` Martin Steigerwald
2016-09-19 14:38 ` David Sterba
2016-09-19 15:27 ` stability matrix (was: Is stability a joke?) David Sterba
2016-09-19 17:18 ` stability matrix Austin S. Hemmelgarn
2016-09-19 19:52 ` Christoph Anton Mitterer
2016-09-19 20:07 ` Chris Mason
2016-09-19 20:36 ` Christoph Anton Mitterer
2016-09-19 21:03 ` Chris Mason
2016-09-19 19:45 ` stability matrix (was: Is stability a joke?) Christoph Anton Mitterer
2016-09-20 7:59 ` Duncan
2016-09-20 8:19 ` Hugo Mills
2016-09-20 8:34 ` David Sterba
2016-09-19 15:38 ` Is stability a joke? David Sterba
2016-09-19 21:25 ` Hans van Kranenburg
2016-09-12 16:27 ` Is stability a joke? (wiki updated) David Sterba
2016-09-12 16:56 ` Austin S. Hemmelgarn
2016-09-12 17:29 ` Filipe Manana
2016-09-12 17:42 ` Austin S. Hemmelgarn
2016-09-12 20:08 ` Chris Murphy
2016-09-13 11:35 ` Austin S. Hemmelgarn
2016-09-15 18:01 ` Chris Murphy
2016-09-15 18:20 ` Austin S. Hemmelgarn
2016-09-15 19:02 ` Chris Murphy
2016-09-15 20:16 ` Hugo Mills
2016-09-15 20:26 ` Chris Murphy
2016-09-16 12:00 ` Austin S. Hemmelgarn
2016-09-19 2:57 ` Zygo Blaxell
2016-09-19 12:37 ` Austin S. Hemmelgarn
2016-09-19 4:08 ` Zygo Blaxell
2016-09-19 15:27 ` Sean Greenslade
2016-09-19 17:38 ` Austin S. Hemmelgarn
2016-09-19 18:27 ` Chris Murphy
2016-09-19 18:34 ` Austin S. Hemmelgarn
2016-09-19 20:15 ` Zygo Blaxell
2016-09-20 12:09 ` Austin S. Hemmelgarn
2016-09-15 21:23 ` Christoph Anton Mitterer
2016-09-16 12:13 ` Austin S. Hemmelgarn
2016-09-19 3:47 ` Zygo Blaxell
2016-09-19 12:32 ` Austin S. Hemmelgarn
2016-09-19 15:33 ` Zygo Blaxell
2016-09-12 19:57 ` Martin Steigerwald
2016-09-12 20:21 ` Pasi Kärkkäinen
2016-09-12 20:35 ` Martin Steigerwald
2016-09-12 20:44 ` Chris Murphy
2016-09-13 11:28 ` Austin S. Hemmelgarn [this message]
2016-09-13 11:39 ` Martin Steigerwald
2016-09-14 5:53 ` Marc Haber
2016-09-12 20:48 ` Waxhead
2016-09-13 8:38 ` Timofey Titovets
2016-09-13 11:26 ` Austin S. Hemmelgarn
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=f5a952b4-09d6-a8f8-161d-16f419c81cb1@gmail.com \
--to=ahferroin7@gmail.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=martin@lichtvoll.de \
--cc=pasik@iki.fi \
--cc=waxhead@online.no \
/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).