mirror of https://lore.kernel.org/lkml/
 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 7.3-rc7
Date: Wed,  7 Oct 2026 15:49:12 +0200	[thread overview]
Message-ID: <cover.1791380069.git.dsterba@suse.com> (raw)

Hi,

please pull a few more fixes, mostly error handling. Half of that is for
io_uring integration with encoded read/write ioctls.

Thanks.

- fix command queuing and cleanup in encoded read/write ioctls

- fix root and transaction association to avoid unnecessary lock
  contention and transaction start

- properly handle replacing multiple xattrs in the same item

- in scrub, fix root reference leak after reporting an unresolved file
  path

----------------------------------------------------------------
The following changes since commit 72de4807ba84da485dda1a91572d66da9149e95a:

  btrfs: derive f_fsid with dev_t only when temp_fsid is active (2026-09-17 19:45:12 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 41c8899d59898f6fa51ceebd2b6e55257191a8ee:

  btrfs: fix lost error return value in btrfs_listxattr() (2026-10-05 16:05:44 +0200)

----------------------------------------------------------------
Filipe Manana (3):
      btrfs: clear BTRFS_ROOT_IN_TRANS_SETUP on early exit from record_root_in_trans()
      btrfs: fix xattr replace when multiple xattrs are packed in the same item
      btrfs: fix lost error return value in btrfs_listxattr()

Wentao Liang (1):
      btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()

Yang Xiuwei (4):
      btrfs: always return -EIOCBQUEUED after btrfs_uring_read_extent_endio
      btrfs: free iov when btrfs_uring_read_extent() fails
      btrfs: unlock inode and extent in caller when io_uring read extent fails
      btrfs: don't stash io_uring encoded data across -EAGAIN

 fs/btrfs/inode.c       |  7 +++----
 fs/btrfs/ioctl.c       | 31 ++++++++++++++++---------------
 fs/btrfs/scrub.c       |  4 +++-
 fs/btrfs/transaction.c |  1 +
 fs/btrfs/xattr.c       | 15 +++++++++++----
 5 files changed, 34 insertions(+), 24 deletions(-)

             reply	other threads:[~2026-10-07 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 13:49 David Sterba [this message]
2026-10-07 14:14 ` 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.1791380069.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

all inboxes | Powered by JetHome®