[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1288640739-3246-1-git-send-email-zohar@linux.vnet.ibm.com>
Date: Mon, 1 Nov 2010 15:45:34 -0400
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: Mimi Zohar <zohar@...ux.vnet.ibm.com>,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, jmorris@...ei.org,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
eparis@...hat.com, viro@...iv.linux.org.uk
Subject: [PATCH v1.1 0/5] IMA: making i_readcount a first class inode citizen
Based on the previous posting discussion, i_readcount is now defined as
atomic.
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 iget_readcount(). Its unclear whether this
call to increment i_readcount should be made earlier, like i_writecount.
The patch ordering is a bit redundant in order to leave removing the ifdef
around i_readcount until the last patch. The first four patches: redefines
i_readcount as atomic, defines iget/iput_readcount(), moves the IMA
functionality in ima_counts_get() to ima_file_check(), and removes the IMA
imbalance code, simplifying IMA. The last patch moves iput_readcount()
to the fs directory and removes the ifdef around i_readcount, making
i_readcount into a "first class inode citizen".
The generic_setlease code could then take advantage of i_readcount.
Mimi
Mimi Zohar (5):
IMA: convert i_readcount to atomic
IMA: define readcount functions
IMA: maintain i_readcount in the VFS layer
IMA: remove IMA imbalance checking
IMA: making i_readcount a first class inode citizen
fs/file_table.c | 16 ++++-
fs/inode.c | 3 +
fs/open.c | 3 +-
include/linux/fs.h | 9 ++-
include/linux/ima.h | 6 --
security/integrity/ima/ima_iint.c | 5 --
security/integrity/ima/ima_main.c | 131 +++++--------------------------------
7 files changed, 43 insertions(+), 130 deletions(-)
--
1.7.2.2
--
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