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.10-rc3, part 2
Date: Fri,  7 Jun 2024 17:18:02 +0200	[thread overview]
Message-ID: <cover.1717771196.git.dsterba@suse.com> (raw)

Hi,

a few more fixes, two are for serious problems which are hard to hit,
details in the changelogs. Please pull, thanks.

- fix handling of folio private changes, the private value holds pointer
  to our extent buffer structure representing a metadata range, release
  and create of the range was not properly synchronized when updating
  the private bit which ended up in double folio_put, leading to all
  sorts of breakage

- fix a crash, reported as duplicate key in metadata, but caused by a
  race of fsync and size extending write, requires prealloc target
  range + fsync and other conditions (log tree state, timing)

- fix leak of qgroup extent records after transaction abort

----------------------------------------------------------------
The following changes since commit f13e01b89daf42330a4a722f451e48c3e2edfc8d:

  btrfs: ensure fast fsync waits for ordered extents after a write failure (2024-05-28 16:35:12 +0200)

are available in the Git repository at:

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

for you to fetch changes up to f3a5367c679d31473d3fbb391675055b4792c309:

  btrfs: protect folio::private when attaching extent buffer folios (2024-06-06 21:42:22 +0200)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: fix leak of qgroup extent records after transaction abort

Omar Sandoval (1):
      btrfs: fix crash on racing fsync and size-extending write into prealloc

Qu Wenruo (1):
      btrfs: protect folio::private when attaching extent buffer folios

 fs/btrfs/disk-io.c   | 10 +--------
 fs/btrfs/extent_io.c | 60 +++++++++++++++++++++++++++-------------------------
 fs/btrfs/tree-log.c  | 17 +++++++++------
 3 files changed, 43 insertions(+), 44 deletions(-)

             reply	other threads:[~2024-06-07 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 15:18 David Sterba [this message]
2024-06-07 22:17 ` [GIT PULL] Btrfs fixes for 6.10-rc3, part 2 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.1717771196.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