Recently I am studying CVE-2016-8660, in https://seclists.org/oss-sec/2016/q4/118, it says that this bug is introduced by commit fc0561cefc04 ("xfs: optimise away log forces on timestamp updates for fdatasync"). And in https://patchwork.kernel.org/patch/9363339/#19693745, david correction has nothing to do with this commit, and is a page lock order bug in the XFS seek hole/data implementation(demsg is in http://people.redhat.com/qcai/tmp/dmesg-sync, Unfortunately, it is not accessible now, I do not understand why this is a page lock order bug). Is this CVE solved? Can I see the demsg in other way? thanks.
