linux-kernel - Re: [v2] gfs2: Fix use-after-free in gfs2_fill

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHMDPKUZgJ80k+u_e45FGSPz5N4sjBfX0AtWu3Oqr79wMSx3MA@mail.gmail.com>
Date: Fri, 2 Jan 2026 17:40:02 +0900
From: Ryota Sakamoto <sakamo.ryota@...il.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: Andreas Grünbacher <agruenba@...hat.com>, 
	gfs2@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	syzbot+4cb0d0336db6bc6930e9@...kaller.appspotmail.com, stable@...r.kernel.org
Subject: Re: [v2] gfs2: Fix use-after-free in gfs2_fill_super()

On Tue, Dec 30, 2025 at 4:46 PM Markus Elfring <Markus.Elfring@....de> wrote:
> Is there a need to indicate a role for the mentioned identifier?

Yes, "fail_threads" is a goto label. And including "label" in the message
explicitly is precise.

> Do you propose to use another label here?

Yes, I am proposing a new label "fail_threads".
I chose this name to maintain consistency with the existing error labels
in this function (e.g., fail_per_node, fail_inodes).

If a v3 is required for other reasons, I will update the commit message
to include "label".

Regards,