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>

1 files changed, 0 insertions, 2 deletions

diff --git a/mm/filemap.c b/mm/filemap.c
index adbac104f34c..100b99c2d504 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -1967,7 +1967,6 @@ inline int generic_write_checks(struct file *file, loff_t *pos, size_t *count, i
         if (unlikely(*pos + *count > MAX_NON_LFS &&
                                 !(file->f_flags & O_LARGEFILE))) {
                 if (*pos >= MAX_NON_LFS) {
-                        send_sig(SIGXFSZ, current, 0);
                         return -EFBIG;
                 }
                 if (*count > MAX_NON_LFS - (unsigned long)*pos) {
@@ -1985,7 +1984,6 @@ inline int generic_write_checks(struct file *file, loff_t *pos, size_t *count, i
         if (likely(!isblk)) {
                 if (unlikely(*pos >= inode->i_sb->s_maxbytes)) {
                         if (*count || *pos > inode->i_sb->s_maxbytes) {
-                                send_sig(SIGXFSZ, current, 0);
                                 return -EFBIG;
                         }
                         /* zero-length writes at ->s_maxbytes are OK */