From: Hongling Zeng <zhongling0719@126.com>
To: Andrew Price <anprice@redhat.com>,
Hongling Zeng <zenghongling@kylinos.cn>,
agruenba@redhat.com, swhiteho@redhat.com,
gregkh@linuxfoundation.org
Cc: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gfs2: Fix use-after-free in gfs2_remove_from_journal()
Date: Thu, 18 Jun 2026 09:50:49 +0800 [thread overview]
Message-ID: <6A334EF9.3080504@126.com> (raw)
In-Reply-To: <d8d1d7fc-4028-4913-8025-cb4c39ab437c@redhat.com>
在 2026年06月17日 18:51, Andrew Price 写道:
> On 17/06/2026 10:01, Hongling Zeng wrote:
>> The function calls brelse(bh) but then continues to access
>> the buffer head through bh->b_private, clear_buffer_dirty(),
>> and clear_buffer_uptodate().
>>
>> After brelse() decreases the reference count, the buffer head
>> may be freed, making the subsequent accesses use-after-free.
> When buffers are pinned their refcount is incremented and the brelse() here is only called for pinned buffers so I'm not convinced that there's a bug.
>
> Callers of gfs2_remove_from_journal() also use the bh afterwards so if there was a use-after-free this patch wouldn't fix it.
>
> Did you see a use-after-free in testing?
>
> Andy
>
Thanks for your detailed explanation! this is not a real bug in
practice, the reference counting protects against real UAF.
I'm seeing smatch warnings :
fs/gfs2/log.c:1044 error: dereferencing freed memory 'bh'
fs/gfs2/log.c:1051 warn: passing freed memory 'bh'
And there are potential concerns:
1. Future maintainers might not understand the ref counting semantics
2. The code pattern (brelse then access) is error-prone
3. smatch warnings clutter output for real issues
>> Fix by moving the brelse(bh) call to the end of the function,
>> after all accesses to bh have been completed.
>>
>> Fixes: e93b100931a4 ("GFS2: Fix slab memory leak in gfs2_bufdata")
>> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
>> ---
>> fs/gfs2/log.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/gfs2/log.c b/fs/gfs2/log.c
>> index 78bba8cc10b8..a92c84146de9 100644
>> --- a/fs/gfs2/log.c
>> +++ b/fs/gfs2/log.c
>> @@ -1038,7 +1038,6 @@ void gfs2_remove_from_journal(struct buffer_head *bh, int meta)
>> set_bit(TR_TOUCHED, &tr->tr_flags);
>> }
>> was_pinned = 1;
>> - brelse(bh);
>> }
>> if (bd) {
>> if (bd->bd_tr) {
>> @@ -1056,6 +1055,8 @@ void gfs2_remove_from_journal(struct buffer_head *bh, int meta)
>> }
>> clear_buffer_dirty(bh);
>> clear_buffer_uptodate(bh);
>> + if (was_pinned)
>> + brelse(bh);
>> }
>>
>> /**
next prev parent reply other threads:[~2026-06-18 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 9:01 [PATCH] gfs2: Fix use-after-free in gfs2_remove_from_journal() Hongling Zeng
2026-06-17 10:51 ` Andrew Price
2026-06-18 1:50 ` Hongling Zeng [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-01 2:18 Hongling Zeng
2026-06-01 5:46 ` Greg KH
2026-05-22 9:43 Hongling Zeng
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=6A334EF9.3080504@126.com \
--to=zhongling0719@126.com \
--cc=agruenba@redhat.com \
--cc=anprice@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
--cc=zenghongling@kylinos.cn \
/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.