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: <ZA8Nl2z4Tl+0wCj6@smile.fi.intel.com>
Date:   Mon, 13 Mar 2023 13:48:39 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
Cc:     Paul Moore <paul@...l-moore.com>,
        Roberto Sassu <roberto.sassu@...wei.com>,
        linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Mimi Zohar <zohar@...ux.ibm.com>,
        Thomas Weißschuh <linux@...ssschuh.net>,
        Casey Schaufler <casey@...aufler-ca.com>,
        Christian Göttsche <cgzones@...glemail.com>,
        Mickaël Salaün <mic@...ikod.net>,
        Frederick Lawler <fred@...udflare.com>
Subject: Re: [PATCH v1 1/2] LSM: add a release() hook for the clean exit
 cleanup of the LSM modules

On Sat, Mar 11, 2023 at 12:11:08AM +0100, Mirsad Goran Todorovac wrote:
> The LSM modules, namely integrity, do not have a clean way to deallocate
> resources allocated in the init() hook or later in their lifetime. The
> resources are destroyed on kernel shutdown in an undefined order.
> 
> This will allow a .release member per LSM module and calling proper
> destructors in a well-behaved order.

...

> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: Mimi Zohar <zohar@...ux.ibm.com>
> Cc: Paul Moore <paul@...l-moore.com>
> Cc: Thomas Weißschuh <linux@...ssschuh.net>
> Cc: Casey Schaufler <casey@...aufler-ca.com>
> Cc: Christian Göttsche <cgzones@...glemail.com>
> Cc: Mickaël Salaün <mic@...ikod.net>
> Cc: Frederick Lawler <fred@...udflare.com>

As I told you, try to use my script instead, run it as

`ge2maintainer.sh -c 2 -v 2 HEAD~0 --annotate --cover-letter`

(assuming your 2 patches are on the top of the current branch
 in the Git tree of Linux kernel source code).

It will create a template for the cover letter, automatically
applies To and Cc lists based on the MAINTAINERS database and
sends them.

-- 
With Best Regards,
Andy Shevchenko


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ