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.6-rc2
Date: Tue, 12 Sep 2023 19:31:21 +0200	[thread overview]
Message-ID: <cover.1694467872.git.dsterba@suse.com> (raw)

Hi,

first batch of fixes for 6.6. Please pull, thanks.

- several fixes for handling directory item (inserting, removing,
  iteration, error handling)

- fix transaction commit stalls when auto relocation is running and
  blocks other tasks that want to commit

- fix a build error when DEBUG is enabled

- fix lockdep warning in inode number lookup ioctl

- fix race when finishing block group creation

- remove link to obsolete wiki in several files

----------------------------------------------------------------
The following changes since commit c02d35d89b317994bd713ba82e160c5e7f22d9c8:

  btrfs: zoned: skip splitting and logical rewriting on pre-alloc write (2023-08-22 14:19:59 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.6-rc1-tag

for you to fetch changes up to 5facccc9402301d67d48bef06159b91f7e41efc0:

  MAINTAINERS: remove links to obsolete btrfs.wiki.kernel.org (2023-09-08 14:21:27 +0200)

----------------------------------------------------------------
Bhaskar Chowdhury (1):
      MAINTAINERS: remove links to obsolete btrfs.wiki.kernel.org

Filipe Manana (6):
      btrfs: fix race between finishing block group creation and its item update
      btrfs: release path before inode lookup during the ino lookup ioctl
      btrfs: fix lockdep splat and potential deadlock after failure running delayed items
      btrfs: improve error message after failure to add delayed dir index item
      btrfs: remove BUG() after failure to insert delayed dir index item
      btrfs: assert delayed node locked when removing delayed item

Josef Bacik (2):
      btrfs: do not block starts waiting on previous transaction commit
      btrfs: check for BTRFS_FS_ERROR in pending ordered assert

Qu Wenruo (1):
      btrfs: fix a compilation error if DEBUG is defined in btree_dirty_folio

 Documentation/filesystems/btrfs.rst |   1 -
 MAINTAINERS                         |   1 -
 fs/btrfs/Kconfig                    |   2 +-
 fs/btrfs/block-group.c              |  12 ++++-
 fs/btrfs/delayed-inode.c            | 104 ++++++++++++++++++++++++------------
 fs/btrfs/disk-io.c                  |  22 ++++----
 fs/btrfs/ioctl.c                    |   8 ++-
 fs/btrfs/locking.h                  |   2 +-
 fs/btrfs/ordered-data.c             |   2 +-
 fs/btrfs/transaction.c              |  39 ++++++++------
 fs/btrfs/transaction.h              |   1 +
 11 files changed, 128 insertions(+), 66 deletions(-)

             reply	other threads:[~2023-09-12 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 17:31 David Sterba [this message]
2023-09-12 18:59 ` [GIT PULL] Btrfs fixes for 6.6-rc2 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.1694467872.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