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: <d41ce2d1-e353-4e5b-a17f-52d888a560b4@web.de>
Date: Wed, 19 Nov 2025 21:06:49 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Pratyush Yadav <pratyush@...nel.org>, kexec@...ts.infradead.org,
 linux-mm@...ck.org, Alexander Graf <graf@...zon.com>,
 Andrew Morton <akpm@...ux-foundation.org>,
 David Matlack <dmatlack@...gle.com>, Mike Rapoport <rppt@...nel.org>,
 Pasha Tatashin <pasha.tatashin@...een.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kho: free chunks using free_page() instead of kfree()

…
> When the commit switched to using the buddy allocator directly, it
> missed updating kho_mem_ser_free() to use free_page() instead of
> kfree().

Would another imperative wording become helpful for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc6#n94

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ