[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1297897693.2524.201.camel@localhost.localdomain>
Date: Wed, 16 Feb 2011 18:08:13 -0500
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, James Morris <jmorris@...ei.org>,
torvalds@...ux-foundation.org, eparis@...hat.com,
viro@...iv.linux.org.uk, Dave Chinner <david@...morbit.com>,
"J. Bruce Fields" <bfields@...ldses.org>,
David Safford <safford@...son.ibm.com>
Subject: Re: [PATCH 0/4] IMA: making i_readcount a first class inode citizen
Hi,
As Linus has already agreed that the i_readcount patches (1 - 4) can be
upstreamed (https://lkml.org/lkml/2010/11/18/670), do I need to do
anything else (eg. send James a request to pull)?
thanks,
Mimi
On Mon, 2011-02-14 at 15:29 -0500, Mimi Zohar wrote:
> This is a repost of patches 1 - 4 of the ima-i_readcount patch set rebased
> against security-testing/#next, as requested a while ago. The patches are
> also available from:
> git://git.kernel.org/pub/scm/linux/kernel/git/zohar/ima-2.6.git/#next
>
> This patchset separates the incrementing/decrementing of the i_readcount,
> in the VFS layer, from other IMA functionality, by replacing the current
> ima_counts_get() call with i_readcount_inc(). Its unclear whether this
> call to increment i_readcount should be made earlier, like i_writecount.
> Currently the call is situated immediately after the switch from put_filp()
> to fput() for cleanup.
>
> Mimi
>
> Mimi Zohar (4):
> IMA: convert i_readcount to atomic
> IMA: define readcount functions
> IMA: maintain i_readcount in the VFS layer
> IMA: remove IMA imbalance checking
>
> fs/file_table.c | 5 +-
> fs/open.c | 3 +-
> include/linux/fs.h | 23 ++++++-
> include/linux/ima.h | 6 --
> security/integrity/ima/ima_iint.c | 5 --
> security/integrity/ima/ima_main.c | 130 ++++---------------------------------
> 6 files changed, 40 insertions(+), 132 deletions(-)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists