linux-kernel - Re: [PATCH v2] kexec: Replace the goto out

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: <A940369E59AD3EAB+ea9d2380-94f1-4c75-a3e9-140a8cf222e2@uniontech.com>
Date: Wed, 17 Dec 2025 10:20:28 +0800
From: Qiang Ma <maqianga@...ontech.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: bhe@...hat.com, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] kexec: Replace the goto out_unlock with out


在 2025/12/17 03:11, Andrew Morton 写道:
> On Tue, 16 Dec 2025 15:55:18 +0800 Qiang Ma <maqianga@...ontech.com> wrote:
>
>> The image is initialized to NULL. Then, after calling kimage_alloc_init,
>> we can directly goto 'out' because at this time, the kimage_free will
>> determine whether image is a NULL pointer.
>>
>> This will prepare for the subsequent patch to reset the variable in
>> kimage_free.
> There doesn't seem to be a benefit to applying this patch unless the
> "subsequent patch" is also applied.  So wouldn't a two-patch series be
> more appropriate?
>
Yes.
This patch is a preparation for the patch series "kexec: add kexec flag 
to control debug printing".
I plan to post it together with the v2 of this patch series.