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: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.18-rc3
Date: Mon, 11 Apr 2022 23:31:43 +0200	[thread overview]
Message-ID: <cover.1649705056.git.dsterba@suse.com> (raw)

Hi,

a few more code fixes and a warning fixes. There's one feature ioctl
removal patch slated for 5.18 that did not make it to the main pull
request.  It's just a one-liner and the ioctl has a v2 that's in use for
a long time, no point to postpone it to 5.19.

Please pull, thanks.

- fixes:
  - add back cgroup attribution for compressed writes
  - add super block write start/end annotations to asynchronous balance
  - fix root reference count on an error handling path
  - in zoned mode, activate zone at the chunk allocation time to avoid
    ENOSPC due to timing issues
  - fix delayed allocation accounting for direct IO

- remove balance v1 ioctl, superseded by v2 in 2012

- warning fixes:
  - simplify assertion condition in zoned check
  - remove an unused variable

----------------------------------------------------------------
The following changes since commit 60021bd754c6ca0addc6817994f20290a321d8d6:

  btrfs: prevent subvol with swapfile from being deleted (2022-03-24 17:50:57 +0100)

are available in the Git repository at:

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

for you to fetch changes up to acee08aaf6d158d03668dc82b0a0eef41100531b:

  btrfs: fix btrfs_submit_compressed_write cgroup attribution (2022-04-06 00:50:51 +0200)

----------------------------------------------------------------
Dennis Zhou (1):
      btrfs: fix btrfs_submit_compressed_write cgroup attribution

Haowen Bai (1):
      btrfs: zoned: remove redundant condition in btrfs_run_delalloc_range

Jia-Ju Bai (1):
      btrfs: fix root ref counts in error handling in btrfs_get_root_ref

Naohiro Aota (4):
      btrfs: release correct delalloc amount in direct IO write path
      btrfs: mark resumed async balance as writing
      btrfs: return allocated block group from do_chunk_alloc()
      btrfs: zoned: activate block group only for extent allocation

Nathan Chancellor (1):
      btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()

Nikolay Borisov (1):
      btrfs: remove support of balance v1 ioctl

 fs/btrfs/block-group.c | 40 +++++++++++++++++++++++++++-------------
 fs/btrfs/block-group.h |  4 ++++
 fs/btrfs/compression.c |  8 ++++++++
 fs/btrfs/disk-io.c     |  5 +++--
 fs/btrfs/extent-tree.c |  2 +-
 fs/btrfs/inode.c       |  9 ++++-----
 fs/btrfs/ioctl.c       |  2 --
 fs/btrfs/volumes.c     |  2 ++
 8 files changed, 49 insertions(+), 23 deletions(-)


             reply	other threads:[~2022-04-11 21:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 21:31 David Sterba [this message]
2022-04-13 11:52 ` [GIT PULL] Btrfs fixes for 5.18-rc3 David Sterba
2022-04-14 14:37 ` David Sterba
2022-04-14 17:50   ` Linus Torvalds
2022-04-14 18:59 ` 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.1649705056.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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