From: Paul Moore <pmoore@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] SELinux fixes for 4.5 (#2)
Date: Tue, 23 Feb 2016 12:01:43 -0500 [thread overview]
Message-ID: <2007254.ryXfPbMQOT@sifl> (raw)
In-Reply-To: <alpine.LRH.2.20.1602232237530.428@namei.org>
On Tuesday, February 23, 2016 10:39:26 PM James Morris wrote:
> On Mon, 22 Feb 2016, Paul Moore wrote:
> > Hi James,
> >
> > One more straightforward patch to fix a problem with the inode
> > invalidation changes. The fix passes the selinux-testsuite and applies
> > cleanly on top of your current linux-security#next branch; please apply.
>
> Where is patch '#1' ?
Where is said it was in the pull request ... ? It is in the usual SELinux
kernel repo, in the stable-4.5 branch. It looks okay on my end, are you
having problems fetching the branch/commit?
git://git.infradead.org/users/pcmoore/selinux stable-4.5
http://git.infradead.org/users/pcmoore/selinux/shortlog/refs/heads/stable-4.5
commit e817c2f33efb4aa7f02c98dfab9a5f8ff383ea7e
Author: Andreas Gruenbacher <agruenba@redhat.com>
Date: Thu Feb 18 12:04:08 2016 +0100
selinux: Don't sleep inside inode_getsecid hook
The inode_getsecid hook is called from contexts in which sleeping is not
allowed, so we cannot revalidate inode security labels from there. Use
the non-validating version of inode_security() instead.
Reported-by: Benjamin Coddington <bcodding@redhat.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
Signed-off-by: Paul Moore <paul@paul-moore.com>
--
paul moore
security @ redhat
prev parent reply other threads:[~2016-02-23 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 19:53 [GIT PULL] SELinux fixes for 4.5 (#2) Paul Moore
2016-02-23 11:39 ` James Morris
2016-02-23 17:01 ` Paul Moore [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=2007254.ryXfPbMQOT@sifl \
--to=pmoore@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
/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.