From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: "Paul Moore" <paul@paul-moore.com>,
"Roberto Sassu" <roberto.sassu@huawei.com>,
linux-kernel@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"Christian Göttsche" <cgzones@googlemail.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Frederick Lawler" <fred@cloudflare.com>
Subject: Re: [PATCH v1 1/2] LSM: add a release() hook for the clean exit cleanup of the LSM modules
Date: Mon, 13 Mar 2023 13:48:39 +0200 [thread overview]
Message-ID: <ZA8Nl2z4Tl+0wCj6@smile.fi.intel.com> (raw)
In-Reply-To: <20230310231107.10954-1-mirsad.todorovac@alu.unizg.hr>
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@linuxfoundation.org>
> Cc: Mimi Zohar <zohar@linux.ibm.com>
> Cc: Paul Moore <paul@paul-moore.com>
> Cc: Thomas Weißschuh <linux@weissschuh.net>
> Cc: Casey Schaufler <casey@schaufler-ca.com>
> Cc: Christian Göttsche <cgzones@googlemail.com>
> Cc: Mickaël Salaün <mic@digikod.net>
> Cc: Frederick Lawler <fred@cloudflare.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
prev parent reply other threads:[~2023-03-13 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 23:11 Mirsad Goran Todorovac
2023-03-10 23:11 ` [PATCH v1 2/2] integrity: Add the release() hook to the integrity LSM module Mirsad Goran Todorovac
2023-03-13 11:48 ` Andy Shevchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZA8Nl2z4Tl+0wCj6@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=casey@schaufler-ca.com \
--cc=cgzones@googlemail.com \
--cc=fred@cloudflare.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mic@digikod.net \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®