Comment 10 for bug 1614038

I also can confirm that this is:
3.13.0-123-generic: /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
4.4.0-81-generic: /sys/kernel/config/cluster/ocfs2/heartbeat/threshold

So where does the change come from and what needs to adapt (kernel or ocfs tools).
It was reported that upstream in the kernel this still would be dead_threshold.

I compared:
Trusty: git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git
Xenial: git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git
Upstream: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

I found that on that level Upstream agrees to have dead_threshold just as trusty does.
So why is Xenial off of that - I found an upstream commit [1] that broke it upstream.
That broken state is in since 4.4 and fixed about now in 4.12 with commit [2].

There also is stable kernel activity on this at [3] for 4.11, [4] for 4.9 and [5] for 4.4

Given that pre-analysis I think it is the kernel team that has/want to look to include updates.
I hope my analysis helps to do so, and I have reassigned by adapting the bug tasks accordingly.

[1]: https://github.com/torvalds/linux/commit/45b997737a80
[2]: https://github.com/torvalds/linux/commit/33496c3c3d7b
[3]: https://www.spinics.net/lists/stable/msg179361.html
[4]: https://www.spinics.net/lists/stable/msg179433.html
[5]: https://www.spinics.net/lists/stable/msg179582.html