Comment 9 for bug 75574

To be clear: it's not a vfat issue: vfat just determines where the file limit is, but as didier comments in bug 63900, the actual generation of SIGXFSZ upon /encountering/ file size limits is a default thing, and is found in mm/filemap.c (the one generated for exceeding rlimits is SUS-mandated and should remain: IMO, the others should be removed, leaving just the return of -EFBIG).