Re: [GIT PULL] IMA bug fixes for 4.16

2018-02-02 Thread James Morris
On Fri, 2 Feb 2018, Mimi Zohar wrote:

> On Fri, 2018-02-02 at 21:07 +1100, James Morris wrote:
> > On Thu, 1 Feb 2018, Mimi Zohar wrote:
> > 
> > > 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.
> > 
> > I'd like to see an acked-by or reviewed-by from the FUSE maintainer 
> > (cc'd), on the FUSE patches.
> 
> Ok.  For now, can you take the first two patches?

Sure.


-- 
James Morris




Re: [GIT PULL] IMA bug fixes for 4.16

2018-02-02 Thread James Morris
On Fri, 2 Feb 2018, Mimi Zohar wrote:

> On Fri, 2018-02-02 at 21:07 +1100, James Morris wrote:
> > On Thu, 1 Feb 2018, Mimi Zohar wrote:
> > 
> > > 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.
> > 
> > I'd like to see an acked-by or reviewed-by from the FUSE maintainer 
> > (cc'd), on the FUSE patches.
> 
> Ok.  For now, can you take the first two patches?

Sure.


-- 
James Morris




Re: [GIT PULL] IMA bug fixes for 4.16

2018-02-02 Thread Mimi Zohar
On Fri, 2018-02-02 at 21:07 +1100, James Morris wrote:
> On Thu, 1 Feb 2018, Mimi Zohar wrote:
> 
> > 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.
> 
> I'd like to see an acked-by or reviewed-by from the FUSE maintainer 
> (cc'd), on the FUSE patches.

Ok.  For now, can you take the first two patches?

Mimi



Re: [GIT PULL] IMA bug fixes for 4.16

2018-02-02 Thread Mimi Zohar
On Fri, 2018-02-02 at 21:07 +1100, James Morris wrote:
> On Thu, 1 Feb 2018, Mimi Zohar wrote:
> 
> > 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.
> 
> I'd like to see an acked-by or reviewed-by from the FUSE maintainer 
> (cc'd), on the FUSE patches.

Ok.  For now, can you take the first two patches?

Mimi



Re: [GIT PULL] IMA bug fixes for 4.16

2018-02-02 Thread James Morris
On Thu, 1 Feb 2018, Mimi Zohar wrote:

> 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.

I'd like to see an acked-by or reviewed-by from the FUSE maintainer 
(cc'd), on the FUSE patches.



> 
> 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(-)
> 

-- 
James Morris




Re: [GIT PULL] IMA bug fixes for 4.16

2018-02-02 Thread James Morris
On Thu, 1 Feb 2018, Mimi Zohar wrote:

> 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.

I'd like to see an acked-by or reviewed-by from the FUSE maintainer 
(cc'd), on the FUSE patches.



> 
> 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(-)
> 

-- 
James Morris