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.8-rc7, part 2
Date: Fri, 1 Mar 2024 14:32:55 +0100 [thread overview]
Message-ID: <cover.1709299316.git.dsterba@suse.com> (raw)
Hi,
a few more fixes. Please pull, thanks.
- fix freeing allocated id for anon dev when snapshot creation fails
- fiemap fixes
- followup for a recent deadlock fix, ranges that fiemap can access
can still race with ordered extent completion
- make sure fiemap with SYNC flag does not race with writes
----------------------------------------------------------------
The following changes since commit c7bb26b847e5b97814f522686068c5628e2b3646:
btrfs: fix data race at btrfs_use_block_rsv() when accessing block reserve (2024-02-22 12:15:12 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.8-rc6-tag
for you to fetch changes up to e2b54eaf28df0c978626c9736b94f003b523b451:
btrfs: fix double free of anonymous device after snapshot creation failure (2024-02-29 22:34:11 +0100)
----------------------------------------------------------------
Filipe Manana (3):
btrfs: fix race between ordered extent completion and fiemap
btrfs: ensure fiemap doesn't race with writes when FIEMAP_FLAG_SYNC is given
btrfs: fix double free of anonymous device after snapshot creation failure
fs/btrfs/disk-io.c | 22 ++++-----
fs/btrfs/disk-io.h | 2 +-
fs/btrfs/extent_io.c | 124 +++++++++++++++++++++++++++++++++++++++++--------
fs/btrfs/inode.c | 22 ++++++++-
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/transaction.c | 2 +-
6 files changed, 139 insertions(+), 35 deletions(-)
next reply other threads:[~2024-03-01 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 13:32 David Sterba [this message]
2024-03-01 20:37 ` [GIT PULL] Btrfs fixes for 6.8-rc7, 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.1709299316.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