All of lore.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.17-rc5
Date: Tue,  2 Sep 2025 20:44:31 +0200	[thread overview]
Message-ID: <cover.1756838388.git.dsterba@suse.com> (raw)

Hi,

please pull a few inode logging fixes in tree-log. Thanks.

- fix a few races related to inode link count

- fix inode leak on failure to add link to inode

- move transaction aborts closer to where they happen

----------------------------------------------------------------
The following changes since commit 74857fdc5dd2cdcdeb6e99bdf26976fd9299d2bb:

  btrfs: fix printing of mount info messages for NODATACOW/NODATASUM (2025-08-13 14:08:58 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-rc4-tag

for you to fetch changes up to 986bf6ed44dff7fbae7b43a0882757ee7f5ba21b:

  btrfs: avoid load/store tearing races when checking if an inode was logged (2025-08-22 00:58:55 +0200)

----------------------------------------------------------------
Filipe Manana (6):
      btrfs: abort transaction on failure to add link to inode
      btrfs: fix inode leak on failure to add link to inode
      btrfs: simplify error handling logic for btrfs_link()
      btrfs: fix race between logging inode and checking if it was logged before
      btrfs: fix race between setting last_dir_index_offset and inode logging
      btrfs: avoid load/store tearing races when checking if an inode was logged

 fs/btrfs/btrfs_inode.h |  2 +-
 fs/btrfs/inode.c       | 50 ++++++++++++++++----------------
 fs/btrfs/tree-log.c    | 78 ++++++++++++++++++++++++++++++++++----------------
 3 files changed, 79 insertions(+), 51 deletions(-)

             reply	other threads:[~2025-09-02 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 18:44 David Sterba [this message]
2025-09-02 20:42 ` [GIT PULL] Btrfs fixes for 6.17-rc5 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.1756838388.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.