Steve Dickson <SteveD@xxxxxxxxxx> writes: > True, but even so... Giving file systems an opt-out option with the > default being out, maybe still have some merit... Making file systems > enable this new type of functionality would cut down on any of the > "surprise" that might occur with this redo ;-) I've been arguing for something slightly different for quite some time: I never liked errno values which have side effects in the kernel yet might be visible to userspace. So why not introduce ERETRYSTALE, a *kernel internal* errno value that userspace will never see and filesystems never accidentally set. The VFS can turn this into ESTALE if it doesn't retry for some reason (e.g. already retried). Thanks, Miklos -- 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
