linux-kernel - Re: dlm: use KMEM_CACHE() in dlm_memory

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <dec3e8d9-0a29-4e9b-afb5-888aaef4780d@web.de>
Date: Thu, 20 Jun 2024 08:33:06 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Alexander Aring <aahringo@...hat.com>,
 David Teigland <teigland@...hat.com>, Hongfu Li <lihongfu@...inos.cn>,
 gfs2@...ts.linux.dev
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: dlm: use KMEM_CACHE() in dlm_memory_init()

>> Can the three passed name strings matter still for the identification
>> of the created caches from this function implementation?
>> https://elixir.bootlin.com/linux/v6.10-rc4/source/fs/dlm/memory.c#L27
>> https://elixir.bootlin.com/linux/v6.10-rc4/source/mm/slab_common.c#L362
>
> probably only for "dlm_cb" that turns into "dlm_callback".
…

Will the development attention grow for deviations of passed name strings
from applied data structure identifiers?

Regards,
Markus