From: Casey Schaufler <casey@schaufler-ca.com>
To: Wenhui Zhang <wenhui@gwmail.gwu.edu>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Ondrej Mosnacek <omosnace@redhat.com>,
selinux@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH] selinux: reorder hooks to make runtime disable less broken
Date: Mon, 9 Dec 2019 09:37:32 -0800 [thread overview]
Message-ID: <95a6c581-f1f2-2f82-732b-90503278ad97@schaufler-ca.com> (raw)
In-Reply-To: <CAOSEQ1pHnxrMyn1qYXzJPaT6Smf1ycVOfHQ7-gkDpzYiq9S=Cg@mail.gmail.com>
On 12/9/2019 8:40 AM, Wenhui Zhang wrote:
> As Casey mentioned.
> When changing this order, would you take some default stackable modules in consideration as well?
The order in which another module sets things up ought not
affect your module in any way.
> I personally is writing a module for my course work, and I am using Selinux and Integrity implementations as a basis, while stacking some new hook implementations on top of this.
> If the underlying Selinux and Integrity module changes the order, would it affect my stacked one please?
> Maybe a centralized memory security blob garbage collection module should be written, such as garbage collection by refcount of the security blob?
The security module infrastructure does not do garbage collection.
Modules are encouraged to not create garbage.
next prev parent reply other threads:[~2019-12-09 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 7:57 [PATCH] selinux: reorder hooks to make runtime disable less broken Ondrej Mosnacek
2019-12-09 7:59 ` Ondrej Mosnacek
2019-12-09 13:21 ` Stephen Smalley
2019-12-09 13:58 ` Stephen Smalley
2019-12-09 17:20 ` Casey Schaufler
2019-12-10 11:27 ` Ondrej Mosnacek
2019-12-10 16:23 ` Casey Schaufler
2019-12-09 16:32 ` Casey Schaufler
[not found] ` <CAOSEQ1pHnxrMyn1qYXzJPaT6Smf1ycVOfHQ7-gkDpzYiq9S=Cg@mail.gmail.com>
2019-12-09 17:37 ` Casey Schaufler [this message]
2019-12-10 11:19 ` Ondrej Mosnacek
2019-12-10 19:29 ` Paul Moore
2019-12-10 19:43 ` Casey Schaufler
2019-12-10 19:50 ` Stephen Smalley
2019-12-10 19:57 ` Casey Schaufler
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=95a6c581-f1f2-2f82-732b-90503278ad97@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=wenhui@gwmail.gwu.edu \
/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;
as well as URLs for NNTP newsgroup(s).