summaryrefslogtreecommitdiff
path: root/lib/ts_bm.c
diff options
context:
space:
mode:
authorMicah Cowan <micah@cowan.name>2007-07-16 10:40:08 +0400
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-16 20:05:43 +0400
commit17973f5af741f1758ed57c5115ca394c22bee159 (patch)
tree0fd340e46f1fbae4ab7aa8d06b26af208a3e83f4 /lib/ts_bm.c
parent1e3e8d91fee56e1ab598b265466dc38033f1b915 (diff)
downloadlinux-17973f5af741f1758ed57c5115ca394c22bee159.tar.xz
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>
Diffstat (limited to 'lib/ts_bm.c')
0 files changed, 0 insertions, 0 deletions