linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: clm@fb.com
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: [PULL] Btrfs fixes for 4.11-rc7
Date: Tue, 11 Apr 2017 18:59:31 +0200	[thread overview]
Message-ID: <cover.1491929895.git.dsterba@suse.com> (raw)

there are some fixes for crashes or use-after-free and one fix to the mount
options handling (user-visible behaviour). Please pull to 4.11, thanks.

----------------------------------------------------------------

The following changes since commit 41a75a6eb2bf4e75e0d93862171bebb3ca4efec7:

  Merge branch 'for-chris-4.11-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.11 (2017-03-29 13:10:25 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-chris-4.11-rc7

for you to fetch changes up to a967efb30b3afa3d858edd6a17f544f9e9e46eea:

  Btrfs: fix potential use-after-free for cloned bio (2017-04-11 18:49:56 +0200)

----------------------------------------------------------------
Adam Borowski (1):
      btrfs: drop the nossd flag when remounting with -o ssd

Liu Bo (3):
      Btrfs: fix invalid dereference in btrfs_retry_endio
      Btrfs: fix segmentation fault when doing dio read
      Btrfs: fix potential use-after-free for cloned bio

 fs/btrfs/inode.c   | 22 ++++++++++------------
 fs/btrfs/super.c   |  3 +++
 fs/btrfs/volumes.c |  2 +-
 3 files changed, 14 insertions(+), 13 deletions(-)

                 reply	other threads:[~2017-04-11 16:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cover.1491929895.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.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;
as well as URLs for NNTP newsgroup(s).