The first one is a workaround for a regression introduced in the Linux client in the current pull requesdt. The second is standards compliance fix to comply with the latest rfc5661 errata on return on close semantics. Changes since v1: - the Linux clients wants to see NOTIFY_DEVICEID4_CHANGE supported as well, which is even more broken as there's basically no sensible way to actually implement NOTIFY_DEVICEID4_CHANGE.. -- 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