On Sun, Jun 4, 2017 at 10:37 PM, Michal Hocko <mhocko@xxxxxxxx> wrote: > Running a distribution kernel is at risk that obscure bugs (like this > one) will be asked to be reproduced on the vanilla kernel. I work to > support a distribution kernel as well and I can tell you that I always > do my best reproducing or at least pinpointing the issue before > reporting it upstream. People working on the upstream kernel are quite > busy and _demanding_ a support for something that should come from their > vendor is a bit to much. I understand that. As I already explained, our kernel has _zero_ code that is not in upstream, it is just 4.9.23 plus some non-mm backports from latest. So my question is, is there any fix you believe that is relevant in linux-next but not in 4.9.23? We definitely can try to backport it too. I have checked the changelog since 4.9 and don't find anything obviously relevant. Meanwhile, I will try to run this LTP test repeatly to see if there is any luck. Thanks. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
