On 2013-12-04 10:31, Christoph Hellwig wrote:
Please just fix ntfs to do the mapping for you, EILSEQ is not an
error the VFS or applications expect either.
How would you propose the mapping to be done? Are you sure about EILSEQ
not being an error that VFS/applications expect, my userspace tools seem
to handle local filesystem returning EILSEQ just fine?
Moreover I think we really should see why nfs goes into permanent I/O
error state when this is triggered. I don't really mind seeing nfs
unhandled error codes in my kernel log and I/O error on the nfs client
when trying to write badly named files but the fact we cannot recover
from the situation (without closing all handles to the open share) is
alarming.
- Antti
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
