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 updates for 6.1-rc7
Date: Fri, 25 Nov 2022 21:47:15 +0100	[thread overview]
Message-ID: <cover.1669400851.git.dsterba@suse.com> (raw)

Hi,

a few more fixes from past two weeks. Please pull, thanks.

- fix a regression in nowait + buffered write

- in zoned mode fix endianness when comparing super block generation

- locking and lockdep fixes:
  - fix potential sleeping under spinlock when setting qgroup limit
  - lockdep warning fixes when btrfs_path is freed after copy_to_user
  - do not modify log tree while holding a leaf from fs tree locked

- fix freeing of sysfs files of static features on error

- use kv.alloc for zone map allocation as a fallback to avoid warnings
  due to high order allocation

- send, avoid unaligned encoded writes when attempting to clone range

----------------------------------------------------------------
The following changes since commit c62f6bec53e63b11112e1ebce6bbaa39ce6f6706:

  btrfs: zoned: fix locking imbalance on scrub (2022-11-07 14:35:25 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.1-rc6-tag

for you to fetch changes up to ffdbb44f2f23f963b8f5672e35c3a26088177a62:

  btrfs: sysfs: normalize the error handling branch in btrfs_init_sysfs() (2022-11-23 16:52:22 +0100)

----------------------------------------------------------------
Anand Jain (3):
      btrfs: free btrfs_path before copying inodes to userspace
      btrfs: free btrfs_path before copying fspath to userspace
      btrfs: free btrfs_path before copying subvol info to userspace

ChenXiaoSong (1):
      btrfs: qgroup: fix sleep from invalid context bug in btrfs_qgroup_inherit()

Christoph Hellwig (2):
      btrfs: zoned: fix missing endianness conversion in sb_write_pointer
      btrfs: use kvcalloc in btrfs_get_dev_zone_info

Filipe Manana (3):
      btrfs: fix assertion failure and blocking during nowait buffered write
      btrfs: send: avoid unaligned encoded writes when attempting to clone range
      btrfs: do not modify log tree while holding a leaf from fs tree locked

Josef Bacik (1):
      btrfs: free btrfs_path before copying root refs to userspace

Zhen Lei (1):
      btrfs: sysfs: normalize the error handling branch in btrfs_init_sysfs()

 fs/btrfs/ctree.c    | 36 ++++++++++++++++++++++++++------
 fs/btrfs/ioctl.c    | 23 ++++++++++++---------
 fs/btrfs/qgroup.c   |  9 +-------
 fs/btrfs/send.c     | 24 +++++++++++++++++++++-
 fs/btrfs/sysfs.c    |  7 +++++--
 fs/btrfs/tree-log.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++----
 fs/btrfs/zoned.c    |  9 ++++----
 7 files changed, 132 insertions(+), 35 deletions(-)

             reply	other threads:[~2022-11-25 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 20:47 David Sterba [this message]
2022-11-25 22:00 ` [GIT PULL] Btrfs updates for 6.1-rc7 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.1669400851.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