[PATCH 2/2] fs: incorrect direct io error handling v8

If generic_file_direct_write() has fail (ENOSPC condition) inside __generic_file_aio_write_nolock() it may have instantiated a few blocks outside i_size in case of non blockdev files. At least ext2, ext3 and reiserfs interpret i_size and biggest block difference as error. Later fsck will complain

[PATCH 2/2] fs: incorrect direct io error handling v8

If generic_file_direct_write() has fail (ENOSPC condition) inside __generic_file_aio_write_nolock() it may have instantiated a few blocks outside i_size in case of non blockdev files. At least ext2, ext3 and reiserfs interpret i_size and biggest block difference as error. Later fsck will complain