Micah Cowan 17973f5af7 Only send SIGXFSZ when exceeding rlimits. ... Some users have been having problems with utilities like cp or dd dumping core when they try to copy a file that's too large for the destination filesystem (typically, > 4gb). Apparently, some defunct standards required SIGXFSZ to be sent in such circumstances, but SUS only requires/allows it for when a written file exceeds the process's resource limits. I'd like to limit SIGXFSZs to the bare minimum required by SUS. Patch sent per http://lkml.org/lkml/2007/4/10/302 Signed-off-by: Micah Cowan <micahcowan@ubuntu.com> Acked-by: Alan Cox <alan@redhat.com> Cc: <reiserfs-dev@namesys.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2007-07-16 09:05:43 -07:00
..
dir.c	[PATCH] mark struct inode_operations const 2	2007-02-12 09:48:46 -08:00
file.c	Only send SIGXFSZ when exceeding rlimits.	2007-07-16 09:05:43 -07:00
getopt.c
getopt.h
inode.c	Remove SLAB_CTOR_CONSTRUCTOR	2007-05-17 05:23:04 -07:00
ioctl.c	Detach sched.h from mm.h	2007-05-21 09:18:19 -07:00
Kconfig
Makefile
mmap.c
ncplib_kernel.c
ncplib_kernel.h
ncpsign_kernel.c
ncpsign_kernel.h
sock.c	ncpfs: make sure server connection survives a kill	2007-03-06 13:26:27 +01:00
symlink.c