public inbox for linux-kernel@vger.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 6.2-rc3, part 2
Date: Fri,  6 Jan 2023 15:38:00 +0100	[thread overview]
Message-ID: <cover.1672944066.git.dsterba@suse.com> (raw)

Hi,

a few more regression and regular fixes. Please pull, thanks.

- regressions:
  - fix assertion condition using = instead of ==
  - fix false alert on bad tree level check
  - fix off-by-one error in delalloc search during lseek

- fix compat ro feature check at read-write remount

- handle case when read-repair happens with ongoing device replace

- updated error messages

----------------------------------------------------------------
The following changes since commit fee4c19937439693f2420a916169d08e88576e8e:

  btrfs: fix fscrypt name leak after failure to join log transaction (2022-12-20 19:43:47 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 2ba48b20049b5a76f34a85f853c9496d1b10533a:

  btrfs: fix compat_ro checks against remount (2023-01-03 16:22:13 +0100)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: fix off-by-one in delalloc search during lseek

Qu Wenruo (5):
      btrfs: add error message for metadata level mismatch
      btrfs: fix false alert on bad tree level check
      btrfs: handle case when repair happens with dev-replace
      btrfs: always report error in run_one_delayed_ref()
      btrfs: fix compat_ro checks against remount

Tanmay Bhushan (1):
      btrfs: fix ASSERT em->len condition in btrfs_get_extent

 fs/btrfs/bio.c            | 11 ++++++++++-
 fs/btrfs/disk-io.c        | 11 ++++++++---
 fs/btrfs/disk-io.h        |  2 +-
 fs/btrfs/extent-io-tree.c |  2 +-
 fs/btrfs/extent-tree.c    |  7 +++++--
 fs/btrfs/extent_io.c      | 30 +++++++++++++++++++++++++-----
 fs/btrfs/file.c           |  2 +-
 fs/btrfs/inode.c          |  2 +-
 fs/btrfs/super.c          |  2 +-
 9 files changed, 53 insertions(+), 16 deletions(-)

             reply	other threads:[~2023-01-06 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 14:38 David Sterba [this message]
2023-01-06 21:19 ` [GIT PULL] Btrfs fixes for 6.2-rc3, part 2 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.1672944066.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox