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.12, part 2
Date: Mon, 23 Sep 2024 13:52:06 +0200 [thread overview]
Message-ID: <cover.1727091859.git.dsterba@suse.com> (raw)
Hi,
a few more patches that I'd still like to get merged before rc1 as they
are fixes for user reported bugs.
Please pull, thanks.
- fix dangling pointer to rb-tree of defragmented inodes after cleanup
- a followup fix to handle concurrent lseek on the same fd that could
leak memory under some conditions
- fix wrong root id reported in tree checker when verifying dref
----------------------------------------------------------------
The following changes since commit bd610c0937aaf03b2835638ada1fab8b0524c61a:
btrfs: only unlock the to-be-submitted ranges inside a folio (2024-09-10 16:51:22 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.12-tag
for you to fetch changes up to 7f1b63f981b8284c6d8238cb49b5cb156d9a833e:
btrfs: fix use-after-free on rbtree that tracks inodes for auto defrag (2024-09-17 17:35:53 +0200)
----------------------------------------------------------------
Filipe Manana (2):
btrfs: fix race setting file private on concurrent lseek using same fd
btrfs: fix use-after-free on rbtree that tracks inodes for auto defrag
Qu Wenruo (1):
btrfs: tree-checker: fix the wrong output of data backref objectid
fs/btrfs/btrfs_inode.h | 1 +
fs/btrfs/ctree.h | 2 ++
fs/btrfs/defrag.c | 2 ++
fs/btrfs/file.c | 34 +++++++++++++++++++++++++++++++---
fs/btrfs/tree-checker.c | 2 +-
5 files changed, 37 insertions(+), 4 deletions(-)
next reply other threads:[~2024-09-23 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 11:52 David Sterba [this message]
2024-09-23 19:06 ` [GIT PULL] Btrfs updates for 6.12, 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.1727091859.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.