From: Teng Liu <27rabbitlt@gmail.com>
To: echelonh@gmail.com
Cc: linux-btrfs@vger.kernel.org, Teng Liu <27rabbitlt@gmail.com>
Subject: Re: [PATCH] fs: btrfs: fix btrfs_ioctl_space_info() slot_count
Date: Mon, 23 Mar 2026 23:34:24 +0100 [thread overview]
Message-ID: <20260323223424.1876676-1-27rabbitlt@gmail.com> (raw)
In-Reply-To: <20260322063935.3951728-1-echelonh@gmail.com>
Applied and tested on v7.0-rc4 in a QEMU VM with btrfs as the root
filesystem.
Verified that BTRFS_IOC_SPACE_INFO (via btrfs fi usage) returns correct
results under normal operation and while running concurrent filesystem
activity (file creation/deletion in a loop).
No kernel warnings or errors observed in dmesg.
It's hard to create a race condition between 2 passes so didn't test whether
before-patch behaviour.
Tested-by: Teng Liu <27rabbitlt@gmail.com>
prev parent reply other threads:[~2026-03-23 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 6:39 [PATCH] fs: btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak Yochai Eisenrich
2026-03-23 14:26 ` David Sterba
2026-03-23 15:03 ` Yochai E
2026-03-23 18:54 ` David Sterba
2026-03-23 22:34 ` Teng Liu [this message]
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=20260323223424.1876676-1-27rabbitlt@gmail.com \
--to=27rabbitlt@gmail.com \
--cc=echelonh@gmail.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