From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: downgrade from kernel 3.17 to 3.10
Date: Wed, 22 Oct 2014 02:24:54 +0000 (UTC) [thread overview]
Message-ID: <pan$18b5d$12e42fd5$14087ab$8f220edb@cox.net> (raw)
In-Reply-To: AB1090E1-4EC9-4E58-BB95-3CE871018DFB@colorremedies.com
Chris Murphy posted on Tue, 21 Oct 2014 12:07:27 -0400 as excerpted:
> One thing I wonder, if going back to kernel 3.14 (or even 3.10), which
> btrfs-progs to use? Is it OK to use 3.17?
The goal is to have userspace entirely backward compatible (well, to the
last incompatible device format change, anyway, which was well before
3.0). So barring bugs, btrfs-progs-3.17 should work just fine with
kernel 3.14 or even 3.10.
Tho do keep in mind that -progs-3.12 was the first release using the new
kernel-synced versioning. Before that the newest full -progs release was
ancient, 0.19, from years earlier, tho there was a 0.20-rc1 somewhere
along the line. So you really do want at least -progs-3.12 because older
than that is ancient, and definitely the best-tested -progs-3.12 kernel
combinations will be the 3.12 and 3.13 kernel series which ran
concurrently (there being no -progs-3.13, so kernel 3.13 was concurrent
to -progs-3.12).
IOW your point about staying within well-tested norms applies here as
well. By far the most tested code-paths will be the ones where kernel
and -progs versions were concurrent to each other, so that's what I'd
recommend sticking with if you want to play it safe and well tested.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-10-22 2:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:13 downgrade from kernel 3.17 to 3.10 Cristian Falcas
2014-10-21 11:26 ` Duncan
2014-10-21 13:18 ` Cristian Falcas
2014-10-21 15:13 ` Robert White
2014-10-21 15:20 ` Robert White
2014-10-21 15:34 ` Cristian Falcas
2014-10-21 15:58 ` Austin S Hemmelgarn
2014-10-21 16:19 ` Chris Murphy
2014-10-21 16:26 ` Chris Murphy
2014-10-21 16:36 ` Julio E. Gonzalez P.
2014-10-21 17:55 ` Cristian Falcas
2014-10-21 16:07 ` Chris Murphy
2014-10-22 2:24 ` Duncan [this message]
2014-10-21 15:04 ` Robert White
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='pan$18b5d$12e42fd5$14087ab$8f220edb@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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