Michal Hocko wrote: > On Sun 04-06-17 17:58:49, Tetsuo Handa wrote: > [...] > > > As I already mentioned in my original report, I know there are at least > > > two similar warnings reported before: > > > > > > https://lkml.org/lkml/2016/12/13/529 > > > https://bugzilla.kernel.org/show_bug.cgi?id=192981 > > > > > > I don't see any fix, nor I see they are similar to mine. > > > > No means for analyzing, no plan for fixing the problems. > > Stop this bullshit Tetsuo! Seriously, you are getting over the line! > Nobody said we do not care. In order to do something about that we need > to get further and relevant information. What I'm asking for is the method for getting further and relevant information. And I get no positive feedback nor usable alternatives. > The first and the most > important one is whether this is reproducible with the _clean_ vanilla > kernel. At this point, distribution kernel users won't get any help from community, nor distribution kernel users won't be able to help community. Even more, you are asking that whether this is reproducible with the clean _latest_ (linux-next.git or at least linux.git) vanilla kernel. Therefore, only quite few kernel developers can involve this problem, for not everybody is good at establishing environments / steps for reproducing this problem. It makes getting feedback even more difficult. According to your LSFMM session ( https://lwn.net/Articles/718212/ ), you are worrying about out of reviewers. But it seems to me that your orientation keeps the gap between developers and users wider; only experienced developers like you know almost all things, all others will know almost nothing. -- 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>
