Al Viro 4a9d4b024a switch fput to task_work_add ... ... 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 <viro@zeniv.linux.org.uk>		2012-07-22 23:57:58 +04:00
..
calibrate.c
do_mounts_initrd.c	init: disable sparse checking of the mount.o source files	2012-05-31 17:49:27 -07:00
do_mounts_md.c	init: disable sparse checking of the mount.o source files	2012-05-31 17:49:27 -07:00
do_mounts_rd.c	init: disable sparse checking of the mount.o source files	2012-05-31 17:49:27 -07:00
do_mounts.c	init: disable sparse checking of the mount.o source files	2012-05-31 17:49:27 -07:00
do_mounts.h
init_task.c
initramfs.c	init: disable sparse checking of the mount.o source files	2012-05-31 17:49:27 -07:00
Kconfig	Merge branch 'akpm' (Andrew's patch-bomb)	2012-05-31 18:10:18 -07:00
main.c	switch fput to task_work_add	2012-07-22 23:57:58 +04:00
Makefile
noinitramfs.c
version.c