From: Luis Henriques <luis@igalia.com>
To: Ali Ahmet Memis <ali@iusegentoo.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] ufs: free the buffer head container in ubh_bforget
Date: Sun, 02 Aug 2026 10:28:29 +0100 [thread overview]
Message-ID: <875x1syipu.fsf@orpheu.olymp> (raw)
In-Reply-To: <20260801024119.12667-1-ali@iusegentoo.com> (Ali Ahmet Memis's message of "Sat, 1 Aug 2026 05:41:13 +0300")
On Sat, Aug 01 2026, Ali Ahmet Memis wrote:
> ubh_bforget() forgets the buffer heads referenced by a struct
> ufs_buffer_head but never frees the container itself, unlike its
> sibling ubh_brelse() which calls kfree() on the way out. The only
> caller, free_full_branch(), allocates the container through ubh_bread()
> while releasing an indirect block during truncate, so every fully
> removed indirect block leaks one ufs_buffer_head. Truncating or
> unlinking a large file then leaks one allocation per indirect block,
> which kmemleak reports with a free_full_branch, ufs_truncate_blocks,
> ufs_evict_inode backtrace.
>
> Free the container after forgetting its buffers, mirroring ubh_brelse().
>
> Luis Henriques posted a fix for this leak in 2018, but it was never
> applied while fs/ufs had no active maintainer, and the leak is still
> present.
It's been a while, and I don't even remember why I was running xfstests
against this filesystem :-)
But the fix still looks OK. My original patch also dropped the 'if', but
that's just a minor detail. I don't know who's using this ufs driver
these days -- each BSD has it's own thing, and it's likely to be risky to
mount a filesystem in rw mode.
Cheers,
--
Luís
> Link: https://lore.kernel.org/all/20180705150415.25070-1-lhenriques@suse.com/
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ali Ahmet Memis <ali@iusegentoo.com>
> ---
> fs/ufs/util.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ufs/util.c b/fs/ufs/util.c
> index dff6f7461..3c65fbef6 100644
> --- a/fs/ufs/util.c
> +++ b/fs/ufs/util.c
> @@ -117,8 +117,10 @@ void ubh_bforget (struct ufs_buffer_head * ubh)
> unsigned i;
> if (!ubh)
> return;
> - for ( i = 0; i < ubh->count; i++ ) if ( ubh->bh[i] )
> - bforget (ubh->bh[i]);
> + for (i = 0; i < ubh->count; i++)
> + if (ubh->bh[i])
> + bforget(ubh->bh[i]);
> + kfree(ubh);
> }
>
> int ubh_buffer_dirty (struct ufs_buffer_head * ubh)
> --
> 2.54.0
>
next prev parent reply other threads:[~2026-08-02 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 2:41 Ali Ahmet Memis
2026-08-02 9:28 ` Luis Henriques [this message]
2026-08-02 11:41 ` [PATCH v2] " Ali Ahmet Memis
2026-08-02 11:45 ` [PATCH] " Ali Ahmet Memis
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=875x1syipu.fsf@orpheu.olymp \
--to=luis@igalia.com \
--cc=ali@iusegentoo.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®