On Wed, Dec 04, 2013 at 01:15:41PM +0200, Antti T?nkyr? wrote: > 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? EILSEQ doesn't have a specified meaning for VFS operations. Of course your app could handle it in some way, but that's your implementation specific way that has not base for it. > 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. No argument on that. Just saying that the mapping you proposed is not a good idea. -- 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
