Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Nicholas D Steeves <nsteeves@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-progs4.4 with linux-3.16.7 (with truncation of extends patch)
Date: Fri, 5 Feb 2016 15:27:55 -0500	[thread overview]
Message-ID: <56B505CB.8080604@gmail.com> (raw)

Hello,

Is it safe to use btrfs-progs-4.4 with linux-3.16.7 patched with the 
following:

linux-3.16.7
Btrfs: fix truncation of compressed and inlined extents
https://git.kernel.org/linus/0305cd5f7fca85dae392b9ba85b116896eb7c1c7

The specific case I'm looking into is when a Debian user sticks with the 
default kernel, but installs btrfs-progs-4.4 from backports.  I've also 
read that there will be some userspace<->kernel compatibility checks 
added to btrfs-progs at some point, but I wasn't able to find recent 
news on its progress.

Kind regards,
Nicholas

             reply	other threads:[~2016-02-05 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 20:27 Nicholas D Steeves [this message]
2016-02-06  5:57 ` btrfs-progs4.4 with linux-3.16.7 (with truncation of extends patch) Duncan
2016-04-06  3:54   ` Nicholas D Steeves

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=56B505CB.8080604@gmail.com \
    --to=nsteeves@gmail.com \
    --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