By the way, Komali went back and tried 4.14.7 and it does exhibit the issue which she originally reported. As noted before, the origin of the new behavior was tracked down to kernel.org:1455cf8 ... Also as noted, Dmitry's patch does not solve the problem.
Casey
