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: <20240621075533.86674-1-lihongfu@kylinos.cn>
Date: Fri, 21 Jun 2024 15:55:33 +0800
From: Hongfu Li <lihongfu@...inos.cn>
To: markus.elfring@....de
Cc: aahringo@...hat.com,
	gfs2@...ts.linux.dev,
	lihongfu@...inos.cn,
	linux-kernel@...r.kernel.org,
	teigland@...hat.com
Subject: Re: [PATCH] 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?

My initial purpose is to replace kmem_cache_create() with KMEM_CACHE().
In my view,there is no problem in unifying passed name strings and
structure identifiers.
Maybe that's wrong,I will resubmit a patch that does not change
"dlm_cb" to "dlm_callback".

thanks,
Hongfu Li

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ