linux-kernel - [PATCH v3 0/3] lib: Extending support for scope-based resource management

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: <ee5f409e-4412-41cd-b8d8-92872770f04d@web.de>
Date: Sat, 12 Oct 2024 17:00:26 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: linux-crypto@...r.kernel.org, kernel-janitors@...r.kernel.org,
 Andrew Morton <akpm@...ux-foundation.org>,
 Herbert Xu <herbert@...dor.apana.org.au>,
 Peter Zijlstra <peterz@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH v3 0/3] lib: Extending support for scope-based resource
 management

From: Markus Elfring <elfring@...rs.sourceforge.net>
Date: Sat, 12 Oct 2024 15:48:05 +0200

Some development ideas were taken into account according to evolving discussions.

Markus Elfring (3):
  crypto: lib/mpi - Extend support for scope-based resource management
  lib/digsig: Use scope-based resource management for two MPI variables
    in digsig_verify_rsa()
  lib/digsig: Use scope-based resource management for two variables
    in digsig_verify_rsa()

 include/linux/mpi.h |   4 ++
 lib/digsig.c        | 107 +++++++++++++++++++++++---------------------
 2 files changed, 59 insertions(+), 52 deletions(-)

V3:
* Applications were added as requested (by Herbert Xu) for the proposed
  programming interface extension.

* Further adjustments were provided for the demonstration of an evolving
  programming interface.

V2:
The kernel build service pointed out that the proposed identifier “T_”
was not recognised by the compiler.
Thus reserved identifiers need still be applied also at such a place instead
so far.
I became curious under which circumstances corresponding development concerns
will be reconsidered any more.

--
2.46.1