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>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.11-rc4
Date: Mon, 11 Jan 2021 22:09:55 +0100	[thread overview]
Message-ID: <cover.1610386850.git.dsterba@suse.com> (raw)

Hi,

more material for stable trees. Please pull, thanks.

- tree-checker: check item end overflow

- fix false warning during relocation regarding extent type

- fix inode flushing logic, caused notable performance regression (since
  5.10)

- debugging fixups:
  - print correct offset for reloc tree key
  - pass reliable fs_info pointer to error reporting helper

----------------------------------------------------------------
The following changes since commit a8cc263eb58ca133617662a5a5e07131d0ebf299:

  btrfs: run delayed iputs when remounting RO to avoid leaking them (2020-12-18 15:00:08 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.11-rc3-tag

for you to fetch changes up to e076ab2a2ca70a0270232067cd49f76cd92efe64:

  btrfs: shrink delalloc pages instead of full inodes (2021-01-08 16:36:44 +0100)

----------------------------------------------------------------
Josef Bacik (2):
      btrfs: print the actual offset in btrfs_root_name
      btrfs: shrink delalloc pages instead of full inodes

Qu Wenruo (1):
      btrfs: reloc: fix wrong file extent type check to avoid false ENOENT

Su Yue (2):
      btrfs: prevent NULL pointer dereference in extent_io_tree_panic
      btrfs: tree-checker: check if chunk item end overflows

 fs/btrfs/disk-io.c      |  2 +-
 fs/btrfs/extent_io.c    |  4 +---
 fs/btrfs/inode.c        | 60 +++++++++++++++++++++++++++++++++++--------------
 fs/btrfs/print-tree.c   | 10 ++++-----
 fs/btrfs/print-tree.h   |  2 +-
 fs/btrfs/relocation.c   |  7 +++++-
 fs/btrfs/space-info.c   |  4 +++-
 fs/btrfs/tree-checker.c |  7 ++++++
 8 files changed, 67 insertions(+), 29 deletions(-)

             reply	other threads:[~2021-01-11 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 21:09 David Sterba [this message]
2021-01-11 22:24 ` [GIT PULL] Btrfs fixes for 5.11-rc4 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.1610386850.git.dsterba@suse.com \
    --to=dsterba@suse.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.