From: Sven Schnelle <svens@linux.ibm.com>
To: rentianyue@tj.kylinos.cn
Cc: Paul Moore <paul@paul-moore.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Eric Paris <eparis@parisplace.org>,
Andreas Gruenbacher <agruenba@redhat.com>,
yangzhao@kylinos.cn, selinux@vger.kernel.org,
Tianyue Ren <rentianyue@kylinos.cn>,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
borntraeger@de.ibm.com
Subject: Re: [PATCH v3 1/1] selinux: fix error initialization in inode_doinit_with_dentry()
Date: Tue, 03 Nov 2020 14:13:25 +0100 [thread overview]
Message-ID: <yt9dh7q64m8a.fsf@linux.ibm.com> (raw)
In-Reply-To: <CAHC9VhR2KPKN8ot9WrkjZQ08X-VPDGkXro18C5jhDEwcFH6wog@mail.gmail.com>
Paul Moore <paul@paul-moore.com> writes:
> On Thu, Oct 8, 2020 at 9:37 PM <rentianyue@tj.kylinos.cn> wrote:
>> From: Tianyue Ren <rentianyue@kylinos.cn>
>>
>> Mark the inode security label as invalid if we cannot find
>> a dentry so that we will retry later rather than marking it
>> initialized with the unlabeled SID.
>>
>> Fixes: 9287aed2ad1f ("selinux: Convert isec->lock into a spinlock")
>> Signed-off-by: Tianyue Ren <rentianyue@kylinos.cn>
>> ---
>> security/selinux/hooks.c | 19 ++++++++++++++++---
>> 1 file changed, 16 insertions(+), 3 deletions(-)
>
> Merged into selinux/next with some minor tweaks to the comments.
> Thanks for your help!
This seems to break booting on s390:
Welcome to Fedora 32 (Thirty Two)!
[ 1.434571] systemd[1]: Set hostname to <xxx.xxx>
[ 1.436839] audit: type=1400 audit(1604408868.681:4): avc: denied { write } for pid=1 comm="systemd" dev="cgroup2" ino=2 scontext=system_u:sys
tem_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0
[ 1.436840] systemd[1]: Failed to create /init.scope control group: Permission denied
[ 1.438039] systemd[1]: Failed to allocate manager object: Permission denied
[ [0;1;31m!!!!!! [0m] Failed to allocate manager object.
[ 1.438281] systemd[1]: Freezing execution.
Any ideas? If i revert 83370b31a915493231e5b9addc72e4bef69f8d31 from
linux-next-20201103 it works fine...
Thanks
Sven
next prev parent reply other threads:[~2020-11-03 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200927094243.43673-1-rentianyue@tj.kylinos.cn>
2020-09-28 3:23 ` [PATCH v1 0/1] selinux: fix error initialization in inode_doinit_with_dentry() Paul Moore
2020-09-28 13:41 ` Stephen Smalley
[not found] ` <tencent_489983C034412A8A6D8DF21D@qq.com>
2020-09-29 12:38 ` Stephen Smalley
[not found] ` <20200927094243.43673-2-rentianyue@tj.kylinos.cn>
2020-09-29 12:54 ` [PATCH v1 1/1] " Stephen Smalley
2020-09-29 13:31 ` Stephen Smalley
2020-09-29 14:18 ` Stephen Smalley
2020-09-30 1:36 ` [PATCH v2 0/1] " rentianyue
2020-09-30 1:36 ` [PATCH v2 1/1] " rentianyue
2020-09-30 13:49 ` Stephen Smalley
2020-10-01 21:14 ` Paul Moore
2020-10-01 21:45 ` Paul Moore
2020-10-09 1:36 ` [PATCH v3 0/1] " rentianyue
2020-10-09 1:36 ` [PATCH v3 1/1] selinux: " rentianyue
2020-10-28 2:17 ` Paul Moore
2020-11-03 13:13 ` Sven Schnelle [this message]
2020-11-03 17:11 ` Paul Moore
2020-11-03 19:02 ` Sven Schnelle
2020-11-04 2:42 ` Paul Moore
2020-11-04 7:01 ` Sven Schnelle
2020-11-04 20:40 ` Paul Moore
2020-10-01 21:41 ` [PATCH v1 " Paul Moore
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=yt9dh7q64m8a.fsf@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=agruenba@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=eparis@parisplace.org \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rentianyue@kylinos.cn \
--cc=rentianyue@tj.kylinos.cn \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=yangzhao@kylinos.cn \
/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.