[PATCH] remove read-only/immutable checks from fat_truncate
From: Christoph Hellwig <hch@lst.de>
There's two callers:
- the truncate path via notify_change, ->setattr, vmtruncate. We
already check for permissions here at the upper level
- fat_delete_inode. This one looks bogus to me - even if we delete
an read-only or immutable inode we want to free the space allocated
by it, else you leak disk blocks.