linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Nicolas Bouchinet <nicolas.bouchinet@clip-os.org>
Cc: linux-integrity@vger.kernel.org, philippe.trebuchet@ssi.gouv.fr,
	dmitry.kasatkin@gmail.com, paul@paul-moore.com,
	jmorris@namei.org, serge@hallyn.com, casey@schaufler-ca.com,
	davem@davemloft.net, lucien.xin@gmail.com, vgoyal@redhat.com,
	omosnace@redhat.com, mortonm@chromium.org,
	nicolas.bouchinet@ssi.gouv.fr, mic@digikod.net,
	cgzones@googlemail.com, linux-security-module@vger.kernel.org,
	brauner@kernel.org, keescook@chromium.org
Subject: Re: [PATCH] evm: Correct inode_init_security hooks behaviors
Date: Tue, 25 Oct 2022 10:22:35 -0400	[thread overview]
Message-ID: <e486cbbd3bbb7faa3b7f3118dc162fdfbc7e3ed6.camel@linux.ibm.com> (raw)
In-Reply-To: <4e645d7cb3c3d8c8c9af944130eb929851d5ba2f.camel@linux.ibm.com>

On Tue, 2022-10-25 at 10:21 -0400, Mimi Zohar wrote:
> On Tue, 2022-10-25 at 15:33 +0200, Nicolas Bouchinet wrote:
> > > Agreed, independently as to whether BPF defines a security xattr, if
> > > two LSMs initialize security xattrs, then this change is needed.  Are
> > > there any other examples?
> > 
> > I think that in its current state the kernel cannot load two LSM capable of xattr
> > initialization as they are all defined with the `LSM_FLAG_EXCLUSIVE` flag set.
> > But I may be unaware of other LSM in development stage.
> 
> Casey, Paul, can we get confirmation on this?
> 
> > > 
> > > (nit: I understand the line size has generally been relaxed, but for
> > > IMA/EVM I would prefer it to be remain as 80 chars.)
> > > 
> > 
> > No problem, will change it !
> > 
> > I'll take time to run few tests with BPF and send a patch v3 with new changes.
> 
> Since Roberto's patches will address the BPF bug(s), is this a fix for
> a real bug or a possbile future one.   Cc'ing stable might not be
> necessary.

And the patch description will need to be updated accordingly.

thanks,

Mimi


  reply	other threads:[~2022-10-25 14:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 13:55 [PATCH] evm: Correct inode_init_security hooks behaviors Nicolas Bouchinet
2022-10-20 15:02 ` Paul Moore
2022-10-21 13:12   ` Nicolas Bouchinet
2022-10-20 15:14 ` Mickaël Salaün
2022-10-21 14:04   ` Nicolas Bouchinet
2022-10-20 16:41 ` Casey Schaufler
2022-10-21 13:17   ` Nicolas Bouchinet
2022-10-20 19:51 ` Mimi Zohar
2022-10-21 13:47   ` Nicolas Bouchinet
2022-10-24 16:35     ` Mimi Zohar
2022-10-25 13:33       ` Nicolas Bouchinet
2022-10-25 14:21         ` Mimi Zohar
2022-10-25 14:22           ` Mimi Zohar [this message]
2022-10-25 15:06           ` Casey Schaufler
2022-10-25 15:58             ` Mimi Zohar
2022-10-26  8:48               ` Nicolas Bouchinet
2022-10-21 14:02 ` Roberto Sassu
2022-10-24 12:50   ` Nicolas Bouchinet

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=e486cbbd3bbb7faa3b7f3118dc162fdfbc7e3ed6.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=brauner@kernel.org \
    --cc=casey@schaufler-ca.com \
    --cc=cgzones@googlemail.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=jmorris@namei.org \
    --cc=keescook@chromium.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=mic@digikod.net \
    --cc=mortonm@chromium.org \
    --cc=nicolas.bouchinet@clip-os.org \
    --cc=nicolas.bouchinet@ssi.gouv.fr \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=philippe.trebuchet@ssi.gouv.fr \
    --cc=serge@hallyn.com \
    --cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).