From: Christoph Hellwig <hch@lst.de>
To: David Sterba <dsterba@suse.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: memory leaks in btrfs raid code in 6.19-rc?
Date: Mon, 26 Jan 2026 05:53:15 +0100 [thread overview]
Message-ID: <20260126045315.GA31641@lst.de> (raw)
When running xfstests on btrfs with a SCRATCH_DEV_POOL and kmemleak
enabled I see a lot of these kmemleak reports, start with btrfs/060,
but affecting basically all tests exercising the RAID code:
unreferenced object 0xffff888111f61890 (size 16):
comm "fsstress", pid 5252, jiffies 4294898624
hex dump (first 16 bytes):
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
backtrace (crc d3088d4f):
__kmalloc_noprof+0x3c8/0x510
alloc_rbio.isra.0+0x127/0x390
raid56_parity_write+0x2b/0x180
btrfs_submit_bbio+0x26d/0x870
submit_one_bio+0x7a/0xb0
submit_extent_folio+0x163/0x320
extent_writepage_io+0x2c9/0x4d0
extent_write_cache_pages+0x396/0x9d0
btrfs_writepages+0x70/0x120
do_writepages+0xc8/0x160
filemap_writeback+0xb3/0xe0
btrfs_fdatawrite_range+0x22/0x60
btrfs_wait_ordered_range+0x47/0x110
btrfs_fallocate+0x193/0x11a0
vfs_fallocate+0x160/0x3c0
__x64_sys_fallocate+0x44/0xa0
next reply other threads:[~2026-01-26 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 4:53 Christoph Hellwig [this message]
2026-01-30 17:18 ` memory leaks in btrfs raid code in 6.19-rc? Filipe Manana
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=20260126045315.GA31641@lst.de \
--to=hch@lst.de \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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