linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	clm@fb.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 4.15-rc2
Date: Wed, 29 Nov 2017 20:28:28 +0100	[thread overview]
Message-ID: <cover.1511980478.git.dsterba@suse.com> (raw)

Hi,

we've collected some fixes in since the pre-merge window freeze. There's
technically only one regression fix for 4.15, but the rest seems important and
candidates for stable. No merge conflicts, please pull, thanks.

- fix missing flush bio puts in error cases (is serious, but rarely happens)

- fix reporting stat::st_blocks for buffered append writes

- fix space cache invalidation

- fix out of bound memory access when setting zlib level

- fix potential memory corruption when fsync fails in the middle

- fix crash in integrity checker

- incremetnal send fix, path mixup for certain unlink/rename combination

- pass flags to writeback so compressed writes can be throttled properly

- error handling fixes

With signed tag: for-4.15-rc2-tag

----------------------------------------------------------------
The following changes since commit d28e649a5c58b779b303c252c66ee84a0f2c3b32:

  btrfs: Fix bug for misused dev_t when lookup in dev state hash table. (2017-11-01 20:45:36 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.15-rc2

for you to fetch changes up to ea37d5998b50a72b9045ba60a132eeb20e1c4230:

  Btrfs: incremental send, fix wrong unlink path after renaming file (2017-11-28 17:15:30 +0100)

----------------------------------------------------------------
David Sterba (2):
      btrfs: add missing device::flush_bio puts
      btrfs: dev_alloc_list is not protected by RCU, use normal list_del

Filipe Manana (3):
      Btrfs: move definition of the function btrfs_find_new_delalloc_bytes
      Btrfs: fix reported number of inode blocks after buffered append writes
      Btrfs: incremental send, fix wrong unlink path after renaming file

Josef Bacik (2):
      btrfs: clear space cache inode generation always
      btrfs: fix deadlock when writing out space cache

Liu Bo (3):
      Btrfs: add write_flags for compression bio
      Btrfs: bail out gracefully rather than BUG_ON
      Btrfs: fix list_add corruption and soft lockups in fsync

Nikolay Borisov (1):
      btrfs: Fix transaction abort during failure in btrfs_rm_dev_item

Qu Wenruo (2):
      btrfs: Fix wild memory access in compression level parser
      btrfs: tree-checker: Fix false panic for sanity test

 fs/btrfs/compression.c           |   9 +--
 fs/btrfs/compression.h           |   5 +-
 fs/btrfs/ctree.h                 |   1 +
 fs/btrfs/disk-io.c               |  10 ++-
 fs/btrfs/extent-tree.c           |  14 ++---
 fs/btrfs/extent_io.c             |   2 +-
 fs/btrfs/extent_io.h             |   8 ++-
 fs/btrfs/file.c                  | 130 +++++++++++++++++++++------------------
 fs/btrfs/free-space-cache.c      |   3 +-
 fs/btrfs/inode.c                 |  34 +++++++---
 fs/btrfs/relocation.c            |   3 +-
 fs/btrfs/send.c                  | 124 +++++++++++++++++++++++++++++++------
 fs/btrfs/super.c                 |  13 +++-
 fs/btrfs/tests/extent-io-tests.c |   6 +-
 fs/btrfs/tests/inode-tests.c     |  12 ++--
 fs/btrfs/tree-checker.c          |  27 ++++++--
 fs/btrfs/tree-checker.h          |  14 ++++-
 fs/btrfs/tree-log.c              |   2 +-
 fs/btrfs/volumes.c               |  32 +++++++---
 19 files changed, 314 insertions(+), 135 deletions(-)

             reply	other threads:[~2017-11-29 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 19:28 David Sterba [this message]
2017-11-29 22:31 ` [GIT PULL] Btrfs fixes for 4.15-rc2 Linus Torvalds
2017-11-30 14:41   ` David Sterba
2019-02-18 10:37 ` Alex Lyakas
2019-02-18 16:15   ` David Sterba

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.1511980478.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).