From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] IMA bug fixes for 4.16
Date: Thu, 01 Feb 2018 13:38:02 -0500 [thread overview]
Message-ID: <1517510282.6675.13.camel@linux.vnet.ibm.com> (raw)
Hi James,
Included in this pull request are three bug fixes, assuming the 2 FUSE
patches are considered bugs and not new features, and a maintainer update.
I'd appreciate your sending them to Linus for 4.16.
thanks,
Mimi
The following changes since commit 36447456e1cca853188505f2a964dbbeacfc7a7a:
ima/policy: fix parsing of fsuuid (2018-01-18 16:52:49 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
for you to fetch changes up to d56f30ac85c067d0d3a6c4f293f655dc298cb5ce:
ima: force re-appraisal on filesystems with FS_IMA_NO_CACHE (2018-02-01 12:38:31 -0500)
----------------------------------------------------------------
Alban Crequy (2):
fuse: introduce new fs_type flag FS_IMA_NO_CACHE
ima: force re-appraisal on filesystems with FS_IMA_NO_CACHE
Mimi Zohar (2):
ima: re-initialize iint->atomic_flags
maintainers: update trusted keys
MAINTAINERS | 1 +
fs/fuse/inode.c | 2 +-
include/linux/fs.h | 1 +
security/integrity/iint.c | 1 +
security/integrity/ima/ima_main.c | 15 +++++++++++++--
5 files changed, 17 insertions(+), 3 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-02-01 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 18:38 Mimi Zohar [this message]
2018-02-02 10:07 ` [GIT PULL] IMA bug fixes for 4.16 James Morris
2018-02-02 14:49 ` Mimi Zohar
2018-02-02 21:31 ` James Morris
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=1517510282.6675.13.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=linux-security-module@vger.kernel.org \
/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).