linux-kernel - Re: btrfs: Simplify the allocation of slab caches in btrfs_delayed_inode

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: <dc42614d-adee-4cf9-96e4-b27604360a9b@web.de>
Date: Thu, 1 Feb 2024 13:07:50 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Kunwu Chan <chentao@...inos.cn>, linux-btrfs@...r.kernel.org,
 kernel-janitors@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Chris Mason <clm@...com>,
 David Sterba <dsterba@...e.com>,
 Johannes Thumshirn <Johannes.Thumshirn@....com>,
 Josef Bacik <josef@...icpanda.com>
Subject: Re: btrfs: Simplify the allocation of slab caches in
 btrfs_delayed_inode_init

…
> So i'll update the commit msg to this:
>
> Use the new KMEM_CACHE() macro instead of direct kmem_cache_create
> to simplify the creation of SLAB caches.
> Make the code cleaner and more readable.
…

* Please replace the word “new” by a reference to the commit 8eb8284b412906181357c2b0110d879d5af95e52
  ("usercopy: Prepare for usercopy whitelisting").

  See also related background information from 2017-06-10.

* How does your response fit to the repetition of improvable change descriptions?

  Example:
  [PATCH] btrfs: Simplify the allocation of slab caches in btrfs_transaction_init
  https://lore.kernel.org/lkml/20240201093554.208092-1-chentao@kylinos.cn/
  https://lkml.org/lkml/2024/2/1/387

* How do you think about to group similar source code transformations
  into patch series?


Regards,
Markus