From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: anon_dev related fixes
Date: Thu, 12 Nov 2026 15:56:32 +1030 [thread overview]
Message-ID: <cover.1794461116.git.wqu@suse.com> (raw)
The first one is a Sashiko bug report, that we have a very narrow window
to hit an anon_dev ID leak.
The second one is another small bug related to double freeing the same
anon_dev ID, exposed by LLM.
Qu Wenruo (2):
btrfs: fix anon_dev leak when snapshot creation races with a root read
btrfs: fix double free of anon_dev in btrfs_get_root_ref() on -EEXIST
fs/btrfs/disk-io.c | 13 +++++++++++++
fs/btrfs/ioctl.c | 8 +-------
2 files changed, 14 insertions(+), 7 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-12 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 5:26 Qu Wenruo [this message]
2026-11-12 5:26 ` [PATCH 1/2] btrfs: fix anon_dev leak when snapshot creation races with a root read Qu Wenruo
2026-11-12 5:26 ` [PATCH 2/2] btrfs: fix double free of anon_dev in btrfs_get_root_ref() on -EEXIST Qu Wenruo
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.1794461116.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.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