linux-toradex.git/fs/file_table.c, branch v3.7

lglock: add DEFINE_STATIC_LGLOCK()

2012-10-10T05:15:44+00:00

When the lglock doesn't need to be exported we can use
DEFINE_STATIC_LGLOCK().

Signed-off-by: Lai Jiangshan 
Cc: Alexander Viro 
Cc: Rusty Russell 
Cc: Andi Kleen 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro

Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security

2012-10-03T04:38:48+00:00

Pull security subsystem updates from James Morris:
 "Highlights:

   - Integrity: add local fs integrity verification to detect offline
     attacks
   - Integrity: add digital signature verification
   - Simple stacking of Yama with other LSMs (per LSS discussions)
   - IBM vTPM support on ppc64
   - Add new driver for Infineon I2C TIS TPM
   - Smack: add rule revocation for subject labels"

Fixed conflicts with the user namespace support in kernel/auditsc.c and
security/integrity/ima/ima_policy.c.

* 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security: (39 commits)
  Documentation: Update git repository URL for Smack userland tools
  ima: change flags container data type
  Smack: setprocattr memory leak fix
  Smack: implement revoking all rules for a subject label
  Smack: remove task_wait() hook.
  ima: audit log hashes
  ima: generic IMA action flag handling
  ima: rename ima_must_appraise_or_measure
  audit: export audit_log_task_info
  tpm: fix tpm_acpi sparse warning on different address spaces
  samples/seccomp: fix 31 bit build on s390
  ima: digital signature verification support
  ima: add support for different security.ima data types
  ima: add ima_inode_setxattr/removexattr function and calls
  ima: add inode_post_setattr call
  ima: replace iint spinblock with rwlock/read_lock
  ima: allocating iint improvements
  ima: add appraise action keywords and default rules
  ima: integrity appraisal extension
  vfs: move ima_file_free before releasing the file
  ...

take fget() and friends to fs/file.c

2012-09-27T01:08:56+00:00

Signed-off-by: Al Viro

vfs: move ima_file_free before releasing the file

2012-09-07T18:57:27+00:00

ima_file_free(), called on __fput(), currently flags files that have
changed, so that the file is re-measured.  For appraising a files's
integrity, the file's hash must be re-calculated and stored in the
'security.ima' xattr to reflect any changes.

This patch moves the ima_file_free() call to before releasing the file
in preparation of ima-appraisal measuring the file and updating the
'security.ima' xattr.

Signed-off-by: Mimi Zohar 
Acked-by: Serge Hallyn 
Acked-by: Dmitry Kasatkin

fs: Add freezing handling to mnt_want_write() / mnt_drop_write()

2012-07-31T05:40:38+00:00

Most of places where we want freeze protection coincides with the places where
we also have remount-ro protection. So make mnt_want_write() and
mnt_drop_write() (and their _file alternative) prevent freezing as well.
For the few cases that are really interested only in remount-ro protection
provide new function variants.

BugLink: https://bugs.launchpad.net/bugs/897421
Tested-by: Kamal Mostafa 
Tested-by: Peter M. Petrakis 
Tested-by: Dann Frazier 
Tested-by: Massimo Morana 
Signed-off-by: Jan Kara 
Signed-off-by: Al Viro

uninline file_free_rcu()

2012-07-29T17:24:17+00:00

What inline?  Its only use is passing its address to call_rcu(), for fuck sake!

Signed-off-by: Al Viro

switch fput to task_work_add

2012-07-22T19:57:58+00:00

... and schedule_work() for interrupt/kernel_thread callers
(and yes, now it *is* OK to call from interrupt).

We are guaranteed that __fput() will be done before we return
to userland (or exit).  Note that for fput() from a kernel
thread we get an async behaviour; it's almost always OK, but
sometimes you might need to have __fput() completed before
you do anything else.  There are two mechanisms for that -
a general barrier (flush_delayed_fput()) and explicit
__fput_sync().  Both should be used with care (as was the
case for fput() from kernel threads all along).  See comments
in fs/file_table.c for details.

Signed-off-by: Al Viro

mark_files_ro(): don't bother with mntget/mntput

2012-07-14T12:35:46+00:00

mnt_drop_write_file() is safe under any lock

Signed-off-by: Al Viro

brlocks/lglocks: API cleanups

2012-05-30T03:28:41+00:00

lglocks and brlocks are currently generated with some complicated macros
in lglock.h.  But there's no reason to not just use common utility
functions and put all the data into a common data structure.

In preparation, this patch changes the API to look more like normal
function calls with pointers, not magic macros.

The patch is rather large because I move over all users in one go to keep
it bisectable.  This impacts the VFS somewhat in terms of lines changed.
But no actual behaviour change.

[akpm@linux-foundation.org: checkpatch fixes]
Signed-off-by: Andi Kleen 
Cc: Al Viro 
Cc: Rusty Russell 
Signed-off-by: Andrew Morton 
Signed-off-by: Rusty Russell 
Signed-off-by: Al Viro

brlocks/lglocks: turn into functions

2012-05-30T03:28:41+00:00

lglocks and brlocks are currently generated with some complicated macros
in lglock.h.  But there's no reason to not just use common utility
functions and put all the data into a common data structure.

Since there are at least two users it makes sense to share this code in a
library.  This is also easier maintainable than a macro forest.

This will also make it later possible to dynamically allocate lglocks and
also use them in modules (this would both still need some additional, but
now straightforward, code)

[akpm@linux-foundation.org: checkpatch fixes]
Signed-off-by: Andi Kleen 
Cc: Al Viro 
Cc: Rusty Russell 
Signed-off-by: Andrew Morton 
Signed-off-by: Rusty Russell 
Signed-off-by: Al Viro