All of lore.kernel.org
 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 5.1-rc3
Date: Tue, 26 Mar 2019 15:15:45 +0100	[thread overview]
Message-ID: <cover.1553608661.git.dsterba@suse.com> (raw)

Hi,

please pull the following tag to receive:

- fsync fixes: i_size for truncate vs fsync, dio vs buffered during
  snapshotting, remove complicated but incomplete assertion

- removed excessive warnigs, misreported device stats updates

- fix raid56 page mapping for 32bit arch

- fixes reported by static analyzer

Thanks.

----------------------------------------------------------------
The following changes since commit d3865159ac7823f645d313fdbac0b256ac01eeb9:

  btrfs: zstd: ensure reclaim timer is properly cleaned up (2019-02-27 17:45:04 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 0ccc3876e4b2a1559a4dbe3126dda4459d38a83b:

  Btrfs: fix assertion failure on fsync with NO_HOLES enabled (2019-03-20 19:53:39 +0100)

----------------------------------------------------------------
Andrea Righi (1):
      btrfs: raid56: properly unmap parity page in finish_parity_scrub()

David Sterba (1):
      btrfs: don't report readahead errors and don't update statistics

Filipe Manana (3):
      Btrfs: fix incorrect file size after shrinking truncate and fsync
      Btrfs: fix file corruption after snapshotting due to mix of buffered/DIO writes
      Btrfs: fix assertion failure on fsync with NO_HOLES enabled

Josef Bacik (1):
      btrfs: remove WARN_ON in log_dir_items

Nikolay Borisov (2):
      btrfs: Fix bound checking in qgroup_trace_new_subtree_blocks
      btrfs: Avoid possible qgroup_rsv_size overflow in btrfs_calculate_inode_block_rsv_size

 fs/btrfs/extent-tree.c |  2 +-
 fs/btrfs/qgroup.c      |  4 ++--
 fs/btrfs/raid56.c      |  3 ++-
 fs/btrfs/transaction.c | 49 +++++++++++++++++++++++++++++++++++++++++++------
 fs/btrfs/tree-log.c    | 33 +++++++++++++++++++++++----------
 fs/btrfs/volumes.c     |  2 +-
 6 files changed, 72 insertions(+), 21 deletions(-)

             reply	other threads:[~2019-03-26 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 14:15 David Sterba [this message]
2019-03-26 17:45 ` [GIT PULL] Btrfs fixes for 5.1-rc3 pr-tracker-bot

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.1553608661.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.