From: Vivek Goyal <vgoyal@redhat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Paul Moore <paul@paul-moore.com>, Stephen Muth <smuth4@gmail.com>,
ceph-devel@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>
Subject: Re: "kernel NULL pointer dereference" crash when attempting a write
Date: Tue, 25 Jan 2022 08:54:24 -0500 [thread overview]
Message-ID: <YfABEFlldUTHL+BH@redhat.com> (raw)
In-Reply-To: <a77ca75bfb69f527272291b4e6556fc46c37f9df.camel@kernel.org>
On Tue, Jan 25, 2022 at 05:54:57AM -0500, Jeff Layton wrote:
[..]
> - /*
> - * FIXME: Make security_dentry_init_security() generic. Currently
> - * It only supports single security module and only selinux has
> - * dentry_init_security hook.
> - */
I think this comment is still very valid. security_dentry_init_security()
still supports only single security module. It does not have the
capability to deal with two modules trying to return security context.
All my patch did was that instead of SELinux, now another LSM could
return security context and also return xattr name for the security
context. But it did nothing to allow multiple LSMs to return their
own security contexts.
IMHO, this FIXME should still be there and not removed.
Thanks
Vivek
next prev parent reply other threads:[~2022-01-25 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM2jsSiHK_++SggmRyRbCxZ58hywxeZsJJMJHpQfbAz-5AfJ0g@mail.gmail.com>
2022-01-25 2:45 ` "kernel NULL pointer dereference" crash when attempting a write Paul Moore
2022-01-25 10:54 ` Jeff Layton
2022-01-25 11:13 ` Christian Brauner
2022-01-25 11:25 ` Jeff Layton
2022-01-25 12:12 ` Christian Brauner
2022-01-25 12:32 ` Jeff Layton
2022-01-25 12:49 ` Christian Brauner
2022-01-25 19:41 ` Paul Moore
2022-01-25 15:56 ` Vivek Goyal
2022-01-25 17:08 ` Casey Schaufler
2022-01-25 19:57 ` Paul Moore
2022-01-25 20:08 ` Casey Schaufler
2022-01-26 0:27 ` Vivek Goyal
2022-01-26 1:00 ` Casey Schaufler
2022-01-26 1:22 ` Stephen Muth
2022-01-26 6:03 ` Serge E. Hallyn
2022-01-25 21:59 ` Vivek Goyal
2022-01-25 13:54 ` Vivek Goyal [this message]
2022-01-25 13:59 ` Christian Brauner
2022-01-25 11:11 ` Christian Brauner
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=YfABEFlldUTHL+BH@redhat.com \
--to=vgoyal@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=jlayton@kernel.org \
--cc=paul@paul-moore.com \
--cc=smuth4@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.