From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Guixiong Wei <weiguixiong@bytedance.com>, <x86@kernel.org>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] x86/fpu: Fix memory leak with dynamic fpstate and exec()
Date: Mon, 19 Oct 2026 10:53:24 -0700 [thread overview]
Message-ID: <89727492-b1d1-4f14-955a-0673ebaee753@intel.com> (raw)
In-Reply-To: <d28dc497-a74b-4c52-bb6c-8b9010f9ee2d@intel.com>
On 10/14/2026 5:19 PM, Chang S. Bae wrote:
> On 10/7/2026 10:59 PM, Guixiong Wei wrote:
>>
>> -void fpstate_free(struct fpu *fpu)
>> +void fpstate_free(struct fpstate *fpstate)
>> {
>> - if (fpu->fpstate && fpu->fpstate != &fpu->__fpstate)
>> - vfree(fpu->fpstate);
>> + if (fpstate && fpstate->is_valloc)
>> + vfree(fpstate);
>> }
>
> Shouldn't is_valloc be cleared here, or when fpstate_reset() replaces
> fpu->fpstate with the embedded fpstate?
No, is_valloc is pat of the vmalloc'ed memory itself.
That said, removing the original check does not seem reassuring either.
Maybe, another option would be adding an internal helper:
void __fpstate_reset(struct fpstate *fpstate)
{
if (fpstate && fpstate->is_valloc)
vfree(fpstate);
}
Then, refactor fpstate_realloc() and replace the vfree() in
fpstate_free() with it, keeping the fpstate_free() prototype unchanged.
Thanks,
Chang
next prev parent reply other threads:[~2026-10-19 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 5:59 [PATCH v2 0/2] x86/fpu: Fix dynamic fpstate leak on exec() Guixiong Wei
2026-10-08 5:59 ` [PATCH v2 1/2] x86/fpu: Fix memory leak with dynamic fpstate and exec() Guixiong Wei
2026-10-15 0:19 ` Chang S. Bae
2026-10-19 17:53 ` Chang S. Bae [this message]
2026-10-20 1:49 ` Guixiong Wei
2026-10-20 1:28 ` Guixiong Wei
2026-10-08 5:59 ` [PATCH v2 2/2] selftests/x86/amx: Test dynamic fpstate cleanup across exec() Guixiong Wei
2026-10-15 0:19 ` Chang S. Bae
2026-10-20 1:59 ` Guixiong Wei
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=89727492-b1d1-4f14-955a-0673ebaee753@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=weiguixiong@bytedance.com \
--cc=x86@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
all inboxes | Powered by JetHome®