Ah, now I see. Thanks for sending the stack trace. On the failure
path, we're calling the inline function ext4_truncate_filaed_write()
and this is calling ext4_truncate().
But I'm now wondering if we need to take the i_data_sem mutex in
ext4_truncate_failed_write().
Otherwise, couldn't we end up with problems where a failed write calls
ext4_truncate() without i_data_sem(), and that races with something
else --- say, a punch or truncate call to that same inode?
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
