I was curious if I could answer Sridhar's question as I had the same question.
The introduction of the problem appears to be in Ubuntu's packaging of select upstream commits from 4.7 to address bug #1647400.
From the comments in that case, it appears 6b4e3181d7bd5ca5ab6f45929e4a5ffa7ab4ab7f should have also been selected.
From looking at the history I gather if I had been running stock 4.4 kernels I would not have been effected by the OOM issue.
I'm basing this on tracking down 0a0337e0d1d134465778a16f5cbea95086e8e9e0 in the main line kernel.
I was curious if I could answer Sridhar's question as I had the same question.
The introduction of the problem appears to be in Ubuntu's packaging of select upstream commits from 4.7 to address bug #1647400.
From the comments in that case, it appears 6b4e3181d7bd5ca 5ab6f45929e4a5f fa7ab4ab7f should have also been selected.
From looking at the history I gather if I had been running stock 4.4 kernels I would not have been effected by the OOM issue.
I'm basing this on tracking down 0a0337e0d1d1344 65778a16f5cbea9 5086e8e9e0 in the main line kernel.